"Stephen Pair" <spair at acm.org> is claimed by the authorities to have written:
 
> But then you'd need to think about much more extensive reworking of how
> Squeak handles directories and files.
Something that is really needed anyway and (at least partially) done in
Flow.

> In the above, you'd need the URI
> object to access the objects in the path sequentially.  For example, it
> first asks "some" to get member "path"; then it asks "path" to get
> member "to"; then it asks "to" to get member "some.zip"; then it asks
> "some.zip" to get member "membername".  Actually, you'd probably want to
> pass the entire remaining portion of the path at each step...details.
The best way of using this pattern is to have a stream on the path and
pass it down to each element; so (whatever object represents) file: gets
the stream from //// to the end, reads from it enough to work out what
to do and passes it on. In a simple case that would be passing it on to
'some' which passes on to 'path' etc. The nice thing is that any
element can swallow up several parts of the path if that is what is
needed, or even un-swallow (I'd say regurgutate but I've just had
dinner) parts.

tim
-- 
Tim Rowledge, tim at sumeru.stanford.edu, http://sumeru.stanford.edu/tim
Hex dump:  Where witches put used curses...