Hi Daniel,

I secretly dream of replacing the Stream hierarchy by Nile. But Nile
is far away from a possible replacement. This is because Nile does not
implement most of the methods that can be found in the Stream
hierarchy. Moreover, replacing the current hierarchy requires a
reimplementation of all subclasses of the class Stream. However, I
think the task is doable. If people want to help making Nile better,
feel free to join.

About the collection hierarchy, I think the replacement is not worth
it. This is because Nathanael refactored the hierarchy using traits
instead of completely reimplementing it. This was the right thing to
do at this time but I would prefer a completely new version, rewritten
from scratch as I did with Nile.

Does this answer all your questions ?

2007/5/14, danil osipchuk <danil at mtsnet.ru>:
>
> Damien,
> this is probably a naive question, but anyway: what do you think -  is it
> possible to replace both collection and stream hierarchies with their
> traitified counterparts and to get a still working image? How much effort
> will it cost (not as a proposal for mainline but as an experiment)
>
> Danil
>
>
> Damien Cassou-3 wrote:
> >
> >
> >
> > Nile has nothing to do with File/Directory classes. It's only for
> > streaming. Yes, you can stream over a file, but our implementation
> > relies on FileDirectory. What Nile aims to replace is ReadStream,
> > WriteStream, StandardFileStream, SocketStream, ZipReadStream...
> >
> >
> >
>
> --
> View this message in context: http://www.nabble.com/-Ann--Nile-0.8.0-available-tf3726678.html#a10609518
> Sent from the Squeak - Dev mailing list archive at Nabble.com.
>
>
>


-- 
Damien Cassou