[antlr-interest] ANTLR C: Question regarding the portability of generated lexer C code

Lego Haryanto legoharyanto at gmail.com
Sat Oct 17 00:04:38 PDT 2009


Thanks, ... yes that's precisely what intend to do ... and you are very
correct, changing that lexer spec isn't going to help.

Best,
-Lego

On Fri, Oct 16, 2009 at 11:27 PM, David-Sarah Hopwood <
david-sarah at jacaranda.org> wrote:

> Jim Idle wrote:
> [...]
> > Change the ranges to:
> >
> > ID: ‘a’..’k’ | ‘l’..’t’ …
>
> I doubt that will work. The generated code sometimes uses character
> literals, sometimes string literals, and sometimes Unicode code point
> values. The code can't be compiled as EBCDIC because the code point
> values are not EBCDIC codes.
>
> It would be easier to hack the C target so that it avoids character
> literals, and uses only \x escapes in string literals.
>
> --
> 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
>



-- 
Fear of the LORD is the beginning of knowledge (Proverbs 1:7)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.antlr.org/pipermail/antlr-interest/attachments/20091017/c8f3c1b8/attachment.html 


More information about the antlr-interest mailing list