Steve,
> > I didn't quite follow the need for #nextOrNil. I also freely
> > admit to not having fully researched it; but it's not widely
> > used in the Squeak images that I use.
>
> It has the same semantics as Squeak's #next. As an example, try evaluating
> the following in both Dolphin and Squeak:
>
> ('a' readStream) next;next
Got it =:0 Similar comments apply to #next:. That makes sense from the
days before exception handling, but it seems these methods should now
complain if asked to read off of the end. FWIW, Flow is said to correctly
raise errors. My Squeak 3.2 image didn't care for it though, and I haven't
yet had a chance to figure out what's happening and why. Thanks for the
heads-up.
> > Also, the implementation you added simply answers nil
> > when the primitive fails, and the other implementations
> > handle things that look like "non-removeable singularities".
>
> Thanks, I agree this is bug that will cause problems for some kinds of
> Streams. I would lean towards re-implementing the method in those Streams,
> rather than testing for atEnd or handling end of stream exceptions. If you
> have any suggestions or fixes, please send them through.
Will do. If you have a chance to try Flow, I'd be curious to know what you
think.
Have a good one,
Bill
--
Wilhelm K. Schwab, Ph.D.
[hidden email]
Locked
