On Jan 19, 2010, at 1:03 PM, Scott Stanchfield wrote: > NIL ;) Ahhh, gotta love the TLAs... > > If you keep the actions to strictly method calls passing > attribute-expressions as values (and don't allow anything else) I'd > think it would keep things simple for use and code generation.
i was thinking something like arbitrary code in some simple imperative language and then any call to @foo() or whatever would call foo in the target language. > I assume you'd still allow target-language-specific actions, too, eh? > Perhaps an option to specify NIL actions (wow - that might be a > confusing name ;) or target-language actions - might be best not to > mix 'em... we'd use language=Java for the target language as we do now and then add perhaps actions=NIL to specify what the actions look like. The default would be actions=language. Perhaps ALE or AIL=ANTLR imperative language? :) T List: http://www.antlr.org/mailman/listinfo/antlr-interest Unsubscribe: http://www.antlr.org/mailman/options/antlr-interest/your-email-address
-- 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]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/il-antlr-interest?hl=en.
