I found the awk script. Just run this on the java file. It will create a new java file, which won't cause the "code too large bug". It was working in ANTLR 3.2, So i think it should work here also.
Gokul. On Wed, Oct 27, 2010 at 12:38 AM, Red Rackham <[email protected]> wrote: > I'm having same issue. Have a big grammar (>900 tokens, >4K lines of > parser > grammar) it's translated from an older source and very messy & > interconnected > since it was generated by conversion script. Was able to get ANTLR to > create > .java files, but the java files don't compile ("code too large"). With > python output, the lexer works up to a point but mis-identifies a token and > I > haven't figured out why... I wanted to debug in ANTLRWorks but I can't > since I > can't get java to compile. Catch 22? > > > > > > List: http://www.antlr.org/mailman/listinfo/antlr-interest > Unsubscribe: > http://www.antlr.org/mailman/options/antlr-interest/your-email-address >
List: http://www.antlr.org/mailman/listinfo/antlr-interest Unsubscribe: http://www.antlr.org/mailman/options/antlr-interest/your-email-address
postprocess.awk
Description: Binary data
-- 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.
