Yep, works fine. I also added some custom @foos for Python. Just
sprinkle your templates with <actions.(actionScope).foo>.
On Tue, Apr 5, 2011 at 6:14 PM, Terence Parr <pa...@cs.usfca.edu> wrote:
> should be fine. I intended the @name to be target dependent. antlr should
> pass all through.
> T
> On Apr 4, 2011, at 8:51 PM, Sam Harwell wrote:
>
> I’m considering the following based on some problems I’ve encountered in the
> past:
>
> To set the accessibility of the generated class:
>
> @lexer::modifier{internal}
> @parser::modifier{internal}
> @modifier{internal} // in a non-combined grammar
>
> To set the accessibility of the constructors of the generated class. In some
> cases, I only want other classes to construct the parser via a custom
> constructor, so it’d be nice to hide the default ones.
>
> @lexer::ctorModifier{private}
> @parser::ctorModifier{protected}
> @ctorModifier{internal}
>
> Sam
>
> _______________________________________________
> antlr-dev mailing list
> antlr-dev@antlr.org
> http://www.antlr.org/mailman/listinfo/antlr-dev
>
>
> _______________________________________________
> antlr-dev mailing list
> antlr-dev@antlr.org
> http://www.antlr.org/mailman/listinfo/antlr-dev
>
>
_______________________________________________
antlr-dev mailing list
antlr-dev@antlr.org
http://www.antlr.org/mailman/listinfo/antlr-dev
