Lego Haryanto wrote: > Jim, thanks for your response ... > > I know that in the EBCDIC system we feed a Unicode stream into the lexer, > thus I'm pretty sure when the generated lexer code I pasted before is > executed, it is already operating on the 32-bit unicode stream. > > The problem is more about the native C compilation in an EBCDIC system like > IBM z/OS mainframe. > > To see if a character from the Unicode stream is an 'A', we have to compare > with a value 0x0041 ... If we match it with a native 'A' in the code, this > will not be a match in an EBCDIC C compilation.
The z/OS C compiler is able to compile in a mode where string and character literals are treated as ISO-8859-1. <http://lists.gnupg.org/pipermail/gcrypt-devel/2009-July/001469.html> -- David-Sarah Hopwood ⚥ http://davidsarah.livejournal.com List: http://www.antlr.org/mailman/listinfo/antlr-interest Unsubscribe: http://www.antlr.org/mailman/options/antlr-interest/your-email-address --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "il-antlr-interest" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/il-antlr-interest?hl=en -~----------~----~----~----~------~----~------~--~---
