> No. We want to collect more information and do more comparisons before moving > away from the recommended Java buffering.
Interesting. Why do you consider it recommended to read one character at a time in a case like this? Maybe there is such a recommendation that I don't know about, but in general I would consider it contrary to expected practice when doing I/O if performance is a concern. Even discounting the fact of ensureOpen() and lock acquisition that seems to be used as per my previous post, even the most efficient implementation I can think of (do some index checking and bump a positional pointer) would still be generally expected to be slower when invoked one character/byte at a time than larger chunks being coped with e.g. System.arraycopy() (though as with all things, within reason; cranking up size too much will of course have other effects such as GC overhead, poorer cache locality, etc). (Note that I'm not arguing the point of whether or not it should be committed before 1.2, but I'm genuinely interested in why not reading one character (or byte) at a time would be a controversial change.) -- / Peter Schuller -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
