Thank you Niall for your exhaustive list, I can't think of anything more to add. Unfortunately most of these are out of date to some degree by now. The most up to date reference is in the package comments, which are also used to generate the pages on the google code site (that's why the odd formatting).
But even the comments largely focus on documenting the API rather than the internals. One aspect that I would highlight, that is likely not apparent from the comments is that at the heart of all the stream types is a single method, #read:into:at: for read streams and #write:from:at: for write streams (this ignores positioning, but that only applies to a subset of streams). This facilitates creation of custom stream classes (transformations or terminals), but also provides clear entry point into an implementation of a particular stream.
"Niall Ross"<
[hidden email]> wrote:
_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc