At 14:53 2/01/2010, Kyle Ferrio wrote: >So, I thought, why not just build and run the target? >Sure, codegen takes a second, and compiling to bytecode takes >another second. So what? Small price for knowing it's right. >Ok, but what about drawing concrete syntax trees? No problem, >just insert actions.
Either I'm misinterpreting what you're talking about, or you're describing what the ANTLRWorks debugger already does. >In fact, it might even be possible to make predicates work in >such an interp, by either "gating off" the callbacks or just >"marking in the debugger" when we're processing a predicate. The problem with predicates is that they're arbitrary target language code; ANTLR simply doesn't have enough information to emulate their functionality (for semantic predicates, at least; syntactic predicates could be dealt with correctly). But that's what the Debug Remote feature is for. 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.
