Hi, I designed everything to be 32 bit clean in terms of token types
and character input so, while \uFFFF is not about character, there is
no reason we can't allow that is input. currently we do not. I set the
maximum to \uFFFE but I am changing it to:
public static final int MAX_CHAR_VALUE = '\uFFFF';
My unit tests and examples directory seemed to work okay. The Java.g
grammar for Sun needs to mimic what the javac compiler does; it allow
us '\uFFFF' and more importantly converts that to the single Unicode
character code point BEFORE the compiler sees it. it is done in the
character string. anyway, ANTLR says that is an invalid character at
the moment. I don't think we will have a problem... can anyone think
of an issue? I do all of my checks using -1 not '\uFFFF' for EOF...we
*should* be okay...
Ter
_______________________________________________
antlr-dev mailing list
[email protected]
http://www.antlr.org:8080/mailman/listinfo/antlr-dev
