Should ReadStream>>next signal EndOfStream?
Helge Horch
Helge.Horch at munich.netsurf.de
Thu May 18 01:35:46 UTC 2000
At 20:09 17.05.2000 -0400, Bob Arning wrote:
>On Thu, 18 May 2000 01:30:36 +0200 Helge Horch
><Helge.Horch at munich.netsurf.de> wrote:
> >[...] as soon as I'm online and snarfing
> >updates, yes, String>>unescapePercents seems to be one case.
> >
> >My question still stands, but I'm aware of caveats. Don't fileIn that
> >changeset into your precious master image.
>
>[...] Some other places:
>
>PositionableStream>>upToEnd
>Base64MimeConverter>>nextValue
>DataStream>>next
Helge, meet Embarassment. Thanks, Bob (again!). Sorry if I broke eekMail...
>make the defaultAction to resume with a nil value. That way old code would
>still work and new code could handle the Exception in a more elegant way.
Thanks for the hint. I did that (all interested parties, find the updated
experimental change set attached), and my sandbox image now reads updates
just fine. I guess my inexperience with the TFEI exception framework shows.
Unless other embarassing flaws remain, I shall release the port tomorrow
(well, actually today, but after a good night's (whatever remains of it)
sleep).
Cheers,
Helge
-------------- next part --------------
A non-text attachment was scrubbed...
Name: EOS.4.cs
Type: application/octet-stream
Size: 1170 bytes
Desc: not available
Url : http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20000518/28754761/EOS.4.obj
More information about the Squeak-dev
mailing list
|