Hi, On Tue, 2003-07-01 at 04:12, Ito Kazumitsu wrote: > In message "Re: [kaffe] Bug report (java.io.StreamTokenizer)" > on 03/07/01, Ito Kazumitsu <[EMAIL PROTECTED]> writes: > > > (From the API doc) Each byte read from the input stream is regarded > > as a character in the range '\u0000' through '\u00FF'. The character > > value is used to look up five possible attributes of the character: > > white space, alphabetic, numeric, string quote, and comment character. > > Each character can have zero or more of these attributes. > > (And I guess) BUT ONLY THE ATTRIBUTE MOST RECENTLY ASSIGNED IS EFFECTIVE.
> Having tested various cases, I have had an impression > that Sun's java.io.StreamTokenizer uses the following > rule: ... > (From the API doc) Each byte read from the input stream is regarded > as a character in the range '\u0000' through '\u00FF'. The character > value is used to look up five possible attributes of the character: > white space, alphabetic, numeric, string quote, and comment character. > Each character can have zero or more of these attributes. > (And I guess) BUT ONLY THE ATTRIBUTE MOST RECENTLY ASSIGNED IS >EFFECTIVE. > ... > And additionally, THE NUMERIC ATTRIBUTE IS KEPT EFFECTIVE EVEN IF > OTHER ATTIBUTES ARE ASSIGNED. > Very good research work Ito! :) Heh...this case is going well beyond the "very interesting" concept... -Hermanni _______________________________________________ kaffe mailing list [EMAIL PROTECTED] http://kaffe.org/cgi-bin/mailman/listinfo/kaffe
