Jim Idle wrote: > If you are sure that the messages are not correct and the lexer rules > are not ambiguous, then you probably need to increase the conversion > timeout: > > -Xconversiontimeout 30000
Ah. I had not realised that this was a wall clock timeout. Perhaps that explains why I occasionally get non-reproducible warnings when ANTLRWorks is running slowly due to Windows being low on memory. Perhaps the "timeout" should be based on some measure of work done rather than wall clock time. That would at least ensure reproducibility for a given grammar and ANTLR version. I assume the units are milliseconds, but <http://www.antlr.org/wiki/display/ANTLR3/Command+line+options> does not document that, or what the default is. -- David-Sarah Hopwood ⚥ http://davidsarah.livejournal.com 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 -~----------~----~----~----~------~----~------~--~---
