[antlr-interest] antlr jar dependency

Chris Black chris at lotuscat.com
Tue Oct 4 08:32:11 PDT 2005


You could use an obfuscator with dead code removal like proguard to trim 
all unneeded classes, methods and fields with respect to what you 
actually use. This would make creating a trimmed down jar easier.

Chris

Akhilesh Mritunjai wrote:

>Hi
>
>Short answer: No
>
>Long answer: Not everything in antlr.jar is actually
>needed for runtime. There is also a separate antlr
>runtime jar file floating somewhere that containes
>only the classes needed at runtime.
>
>Basically, you can load the generate files in
>eclipse/IDEA/netbeans/whatever and remove unncessary
>imports. Then just pack the ones left, and ship your
>product.
>
>I looked at it sometime back, and needed class file
>were south of 100kB or so.
>
>- Akhilesh
>
>--- Alessandro Di Bella <aldib at fuurou.org> wrote:
>
>  
>
>>Hi,
>>I'm new to ANTLR and I need to write a parser that
>>needs to be shipped within 
>>an applet. Because of size restrictions, I was
>>wondering if there was a way 
>>of generating code that did not rely at runtime on
>>the antlr.jar file (like 
>>javacc does).
>>
>>Thanks
>>
>>Alessandro 
>>
>>    
>>
>
>
>
>		
>__________________________________ 
>Yahoo! Mail - PC Magazine Editors' Choice 2005 
>http://mail.yahoo.com
>  
>



More information about the antlr-interest mailing list