Damien,
I have been aware of Flow for some time, but have reasons to avoid it, at least for now. When I tried it some time ago, Nile did not raise any type of exception on reading off the end of a stream (and AFAIK, I was using its streams vs. Squeak's). I have since seen that is supposed to work, so I will take another look.
Bill
Wilhelm K. Schwab, Ph.D. University of Florida Department of Anesthesiology PO Box 100254 Gainesville, FL 32610-0254
Email: bschwab@anest.ufl.edu Tel: (352) 846-1285 FAX: (352) 392-7029
damien.cassou@gmail.com 11/27/2007 2:04 AM >>>
2007/11/27, Matthew Fulmer tapplek@gmail.com:
On Mon, Nov 26, 2007 at 01:00:31PM -0500, Bill Schwab wrote:
I respectfully disagree. AFAICT, the I/O group is dormant, and the
main
list has made its feelings clear.
However, there might be an argument for those interested to take
this to
the I/O list. Any takers?
I subscribed to the io list
the IO list may be appropriate, but the Flow list is probably better. Note that there are currently two alternative stream libraries in squeak (alternative meaning not in squeak.org)
- Flow, which requires a plugin and supports many kinds of external streams, like USB streams and MIDI streams, in addition to collection streams and file streams. It is a major component of Spoon, and is not compatable with squeak's default stream library. See http://netjam.org/flow and http://netjam.org/spoon
- Nile is a refactoring of the squeak stream library. It provides It does collection streams and file streams in two API's. The new API is much simpler than the squeak library, and is incompatable with it. The old API is compatable with squeak stream library. Nile uses traits to share code between the two API's. It does not provide any capabilities beyond the squeak libraries, as far as I can tell. See
http://lists.squeakfoundation.org/pipermail/squeak-dev/2007-November/122481....
Moreover, Nile is maintained by someone who gives the code to the community and let it play with it and commit directly to the main repository. Nile has a lot of unit tests too. If you want to play with it, feel free. You can ask me any question.
Bye
2007/11/27, Bill Schwab BSchwab@anest.ufl.edu:
I have been aware of Flow for some time, but have reasons to avoid it, at least for now. When I tried it some time ago, Nile did not raise any type of exception on reading off the end of a stream (and AFAIK, I was using its streams vs. Squeak's). I have since seen that is supposed to work, so I will take another look.
It still does not raise any exception because this is what ANSI says IIRC. But I don't really care about ANSI anymore so if you want to change the behavior of Nile please do and commit to the main repository. Nile is designed to be easily changeable and extendable.