1 Apr 2005 07:03
Re: [groovy-dev] Unicode Scanners and java.g
Jeremy Rayner wrote: > Hiya, > In lieu of trawling through the historical copies of java.g, what are the > reasons in Michael Studman's latest copy for having the scanner use > the following... > > charVocabulary='\u0003'..'\u7FFE' > > I understand of course that the top end of this (8bit unicode I assume) is not > treading on the toes of EOF (i.e. \u7FFF as per > http://www.antlr.org/doc/lexer.html#unicode ) > > But why are the 3 characters '\u0000', '\u0001' and '\u0002' left out? > What are the design decisions behind that? > > > Thanks for a great tool Ter, Groovy is on the cusp of releasing it's > first antlr based groovy compiler very soon now, yay. > I have read http://www.antlr.org/doc/lexer.html#unicode whers charVocabulary is defined as: charVocabulary='\u0000'..'\uFFFE'; That is, I mean that the 3 characters '\u0000', '\u0001' and '\u0002' should be contained in scanning characters. I have written a Java example and a Groovy example.(Continue reading)
It's always the same URL as usual:
RSS Feed