[antlr-interest] Import problem when antlr is in non-standard package

Mark Gressett Mark.Gressett at sas.com
Mon Oct 17 14:46:43 PDT 2005


Hi everyone,

I'm using antlr 2.7.2 from within ant.  For reasons not entirely clear to me, in our part of the build we use antlr unmodified but packaged into com.sas.solutions.antlr.  The standard ant task for antlr hardwires the antlr package, so I tried a java task with the modified package name, i.e., <java classname="com.sas.solutions.antlr.Tool" ...>

In the generated lexer and parser java files, I end up with import statements like import com.sas.solutions.antlr.TokenStream;
import com.sas.solutions.antlr.ANTLRHashString;
import com.sas.solutions.antlr.LexerSharedInputState;
import com.sas.solutions.com.sas.solutions.com.sas.solutions.antlr.collections.impl.BitSet;

Some are correct, but anything in collections.impl is prefixed with extra stuff.

Is this a known bug that's been fixed in a later release?

Thanks,
Mark


More information about the antlr-interest mailing list