I'm using the Java target with ANTLR 3.2, and having a problem in a rule in my
parser grammar that looks like this:
"variableInit [ String name ]
: ASSIGNMENT id=initializer
-> ^(ASSIGNMENT IDENTIFIER[$ASSIGNMENT, $name] initializer)"
In a particular case where the 'initializer' rule fails
On Tue, 2010-05-25 at 21:12 +0200, Sameh W. Zaky wrote:
> Hi all,
>
> Using ANTLR v3.2, in the runtime I generate the lexer and parser Java files
> using this code:
> org.antlr.Tool.main(new String[]{projectPath+"GrammarFile.g"});
>
> The problem is that, after this line of code, no other code ge
Hi all,
Using ANTLR v3.2, in the runtime I generate the lexer and parser Java files
using this code:
org.antlr.Tool.main(new String[]{projectPath+"GrammarFile.g"});
The problem is that, after this line of code, no other code gets executed,
for example, in this piece of code:
System.out.println("B
Hi,
I want to parse a stream from a serial port. There are packages
like
"T12346679FF22\r\n" which com in all 2 minutes. I want to
lex/parse them
at the moment they arrive.
Using
ANTLRInputStream input = new ANTLR
Thanks for the reply, Jim. I understand the rationale for your suggestion.
Might this info be worth adding to the wiki? It may be obvious to
seasoned hands, but difference in constraints between lexer and parser
rules would be helpful especially since both rule types share the same
basic syntax
Hello :-
This grammar still has the same compilation problem as the one that you
posted yesterday. did you change anything?
I fixed the STRING_LITERAL rule as you suggested in a private e-mail to
me (please keep all messages on this list).
I then did not get any ClassCastException. But got r
