On Wed, 23 Oct 2002, Dalibor Topic wrote: > > Actually, the switch to method b fixed one bug by > > introducing another ;) > Yeah, sorry about that. Could you try the attached > patch and see if it works in your context? It is an > attempt to get the best of both worlds, and runs your > test case as expected.
Thanks for the fast response, yeah the patch does work... However, it's starting to get worrisomely complex. In particular, if for some reason there's a break in the stream right between the cr and lf, which could easily happen with IP-frames etc., it'll lead to hard to track down problems. It may be best to apply that for now, but on the logn run I'd still like to see skipNextLF moved to lower level, possibly native code. This remaidns me of a related optimization issue, is there any kind of plicy/guideline on native code vs. Java in the default lib? It seems implemnting at least some of the more trivial IO classes in native code could yield significant speed-ups for them. -Jukka Santala _______________________________________________ kaffe mailing list [EMAIL PROTECTED] http://kaffe.org/cgi-bin/mailman/listinfo/kaffe
