[antlr-interest] ANTLR C: Question regarding the portability of generated lexer C code
jimi at temporal-wave.com
Fri Oct 16 03:07:22 PDT 2009
ANTLR works internally with 32 bit Unicode (UTF32), not EBCDIC, even if it is in 8 bit mode. So you need to convert the EBCDIC to Unicode 8 bits and use the ‘ASCII’ input stream. A simple way to do this would be to write your own EBCDIC input stream that just converted to Unicode code points (essentially EBCDIC->ASCII) on the fly via a lookup table. Trivial and should be pretty quick.
From: antlr-interest-bounces at antlr.org [mailto:antlr-interest-bounces at antlr.org] On Behalf Of Lego Haryanto
Sent: Tuesday, October 13, 2009 3:51 AM
To: antlr-interest at antlr.org
Subject: [antlr-interest] ANTLR C: Question regarding the portability of generated lexer C code
I just recently noticed that the generated code from my lexer grammar contains something like the following snippet:
else if ( (((LA17_0 >= 'A') && (LA17_0 <= 'Z'))) )
else if ( (((LA17_0 >= 'a') && (LA17_0 <= 'z'))) )
else if ( (((LA17_0 >= 0x00A0) && (LA17_0 <= 0xD7FF))) )
The generated code seems to comfortably use 'A' ... 'Z' literals. This may not be good if let's say I compile the generated code in an IBM z/OS EBCDIC environment as ['A' .. 'Z'] range contains more than just the 26 alphabet codes and the value of the codes are not the same as the ones in Unicode character set.
I'm expecting something like in the third expression where 'A' is written explicitly as 0x0041 (Unicode for 'A').
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the antlr-interest