streams, file{,names} (was "Wanna do something?")

Craig Latta Craig.Latta at NetJam.ORG
Mon Jun 19 23:41:11 UTC 2000


Hi Stefan--

> Sure, we shouldn't start from scratch if somebody already has a better
> solution.  However, the Stream protocol should stay compatible and I always
> thought that Craig's code works with a different design pattern.

	I don't think so. It maintains interface compatibility. I've used it
with the latest Squeak for some time, without incident. The biggest
change I made was probably making internal streams signal an exception
rather than answer nil when asked to answer past the end of a sequence.
Actually, that was discussed a bit on the list a while ago (I'm a month
behind at the moment). Interested parties might like to look at my
changes (http://netjam.org/flow/streaming.zip) to see some of the
methods which rely on the answer-nil behavior. The last time I checked
it deeply was 6 April '99, though (way back at Squeak 2.3).

	The non-standard things in flow are its socket primitives and the
exception-handling support it uses.

> A general URL class is another good thing but I personally would feel
> more comfortable with an old-fashioned File class for now.

	I prefer to separate resources from resource names (e.g., Filename and
File classes).


-C

--
Craig Latta
composer and computer scientist
craig.latta at netjam.org
www.netjam.org
crl at watson.ibm.com
Smalltalkers do: [:it | All with: Class, (And love: it)]





More information about the Squeak-dev mailing list