[antlr-interest] Re: proposal for 2.7.4: charVocabulary defaults to ascii 1..127

[lgcraymer]

Oliver--

Ok, so maybe I should have said

charVocabulary = "UTF-8";

and UTF-16.  The point is more that named character sets have an
advantage in that error messages can be issued.  Ter's example of
"Korean" is one that would pretty clearly not be recognized.  Many of
the vocabulary problems are failure to specify a range, but "Does
ANTLR support unicode" is a close second.

--Loing


--- In antlr-interest at yahoogroups.com, Oliver Zeigermann <oliver at z...>
wrote:
> lgcraymer wrote:
> 
> > Ter--
> > 
> > How about taking the next step?  That is, support
> > 
> > charVocabulary = "ASCII";
> > 
> > and
> > 
> > charVocabulary = "unicode";
> 
> How would that look like? UTF-8? UTF-16? Something else?
> 
> Oliver



 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
     http://groups.yahoo.com/group/antlr-interest/

<*> To unsubscribe from this group, send an email to:
     antlr-interest-unsubscribe at yahoogroups.com

<*> Your use of Yahoo! Groups is subject to:
     http://docs.yahoo.com/info/terms/