Hello Jim, The bug is very strange and I made many tests in order to identify the problem.
It is due to comments inserted in scope declarations. Sometimes they are accepted; in other cases no. It is impossible for me to know why. When there is a problem, lines like: // $myscope::varname = 0; also give an error even if they are comments. I cancelled all the comments in scope declarations and it works perfectly well. Thanks, Claude --------------------------------------------------------------------- From: "Jim Idle" <[email protected]> Subject: Re: [antlr-interest] Global Dynamic Scope To: "[email protected]" <[email protected]> Message-ID: <[email protected]> Content-Type: text/plain; charset="us-ascii" Do you have a small(ish) reproducible example? Jim From: [email protected] [mailto:[email protected]] On Behalf Of Claude Moulin Sent: Tuesday, November 10, 2009 1:47 AM To: [email protected] Subject: [antlr-interest] Global Dynamic Scope Hello, I get a strange error using global scope. I use antlr 3.2. In a tree grammar I define a global scope << pilep >> with several attributes including one called binit. I get several times strange error messages like: unknown dynamically-scoped attribute for scope pilep: binit It seems that sometimes antlr doesn't succeed to translate $pilep::binit into ((pilep_scope)pilep_stack.peek()).binit As it does with other scope attributes. I don't understand the reason. Any idea ? Thanks, Claude -- 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]. For more options, visit this group at http://groups.google.com/group/il-antlr-interest?hl=.
List: http://www.antlr.org/mailman/listinfo/antlr-interest Unsubscribe: http://www.antlr.org/mailman/options/antlr-interest/your-email-address
