On Tue, 2008-09-30 at 11:40 +0100, David Wigg wrote: > To whom it may concern,
> > For our information, I also have a C runtime version. This version > does not seem to work in quite the same way as the Java version in > that the block data appears to be popped before performing any @after > processing (instead of after any @after processing as in the Java > runtime) so that any appropriate block data is no longer available.. Yes - I keep trying to tell people not to rely on @after in the C target as the seeming fix to just move it about in the C.stg isn't quite a simple as it looks because there are many dependencies on what you have in there (predicates, backtrack, scopes and so on). I do need to schedule proper time to look at this and see if this is fixable such that it does everything in the right order in all combinations, but that time won't be until next week right now. Please upgrade to 3.1.1 when it comes out later today by the way. In the main, this update removes dup() code in tree builders that was there for the beta and should not have been left in 3.1 as it causes huge memory consumption and so on. Jim > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
List: http://www.antlr.org:8080/mailman/listinfo/antlr-interest Unsubscribe: http://www.antlr.org:8080/mailman/options/antlr-interest/your-email-address
