Well, the current version of Lark really doesn't really support anything
*but* character streams... that and synchronization, if my measurements
are correct, amount to >50% of the difference between XP and Lark.
It is clear and (sigh) not surprising that method-dispatch-per-char
is, well, less than optimal. Thus my plan had been to move to
a three-arg-read read call.
As a result of this, I'm a bit conflicted about James' suggestion that
we lose the int read() methods. While they are a surefire way
to run slow, I spent enough years in Unix that doing things via
getc() feels natural and I appreciate its advantages; assuming
of course that getc() is a macro with buffering, which of course
a Java method dispatch, uh, isn't. Nice thing about stdio is it made
it easy for the programmer to pretend to do character streams without
having to really do serious per-char work. -T.