commit-classpath
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[commit-cp] [bugs #4742] java.io.StreamTokenizer behaves differently fro


From: Mark Wielaard
Subject: [commit-cp] [bugs #4742] java.io.StreamTokenizer behaves differently from Sun's implementation
Date: Tue, 1 Mar 2005 16:07:03 +0000
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20050105 Galeon/1.3.19 (Debian package 1.3.19-1)

Follow-up Comment #4, bugs #4742 (project classpath):

This might be an obscure interaction with parseNumbers() which sets all
numbers, '.' and '-' to trigger nextToken() to set ttype to TT_NUMBER and
nval to the parse number. The JCL book says that "Once parseNumbers() has
been invoked, the only way to undo its effects is to call ordinaryChar() or
wordChars() explicitly on those chars and the default StreamTokenizer
constructor calls parseNumbers(). So presumably calling resetSyntax() and
then setting any number to a comment char would result in a "normal" parse
with number being treated either as real digits or as real comment chars.

If we decide to emulate this behavior we should document this very clearly.
(More clearly then I did above!) So people are not surprized by this.



    _______________________________________________________

This item URL is:

  <http://savannah.gnu.org/bugs/?func=detailitem&item_id=4742>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/





reply via email to

[Prev in Thread] Current Thread [Next in Thread]