On Fri, 2003-08-08 at 17:13, Andreas Raab wrote:
> > (ReadStream on: #(1 2 3 4 5) from: 3 to: 3) size
> > 
> > Returns 3.
> > 
> > I have to disagree that size is properly implemented.
> 
> No, #size is perfectly well implemented. Trust me ;-) What's wrong is the
> implementation of streams, the mismatch between streams and collections to
> recognize the similarity of the two. For example, if we merely say that:
> 
> Stream		Collection		Meaning
> -------------------------------------------------------------
> readLimit		tally			Actual number of elements
> 

On last thing and I'll let this go for now (which I already said I would
do and then didn't) what does an answer of 3 in this example mean?  I
could understand an answer of 1 which is the length of the indicated
subset or an answer of 5 which is the size of the complete collection. 
But 3 doesn't seem to have any meaning to a user of a Stream that could
be associated with size.

Ken

> Cheers,
>   - Andreas
> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20030808/a12c2d10/attachment.pgp