On Apr 30, 2004, at 9:35 AM, Leopold Toetsch wrote:
Jeff Clites <[EMAIL PROTECTED]> wrote:
Yes, my intention there was for read-as-strings, you'd push a string-ification layer onto the stack. For byte-wise IO, you wouldn't.
Ok. I/O maintainers, please jump in.
And my thoughts in this regard, to be more specific, is that each layer has a top and a bottom (as in the current design), and each "side" is either string-oriented or byte-oriented. So you could potentially have byte-byte (eg, buffering), string-byte, byte-string, and string-string layers (some being more common than others). The "bottom" layer is special--its "top" side works in bytes, and it doesn't really have a bottom (that's the OS interface). To read strings, you need a string-byte layer (if the nomenclature is top-bottom), and for such a layer you need to specify an encoding. You just have to match round pegs to round holes and square pegs to square holes as you stack them.
BTW, I've seen the phrase "IO filter" a few places, but not a definition. What are these supposed to be?
JEff
