Ok, one can easily set ANTLR options from within ANTLRworks (didnt see it, sorry!), to generate code using ANTLRworks. But still, this does not help visualizing the ambiguity :-/ The console shows the same error as the command line version from ANTLR, but it seems to be ignored by ANTLRworks ....
Andreas Andreas Meyer schrieb: > Hi! > > I have a grammar that imports many subgrammars, which in turn import > other sub-grammars. Now, via command-line, ANTLR reports about > ambiguities (displayed as a list of NFA states). Now, in order to > visualize this ambiguity warning in ANTLR, I tried ANTLRworks. However, > this seems to have problems with imported grammars, as it checks the > root grammar in one second and does not report any ambiguity warnings > (whereas the command-line antlr takes several minutes). What can I do? > Note that getting at the ambiguity warnings by "generating code" from > inside ANTLRworks is not possible, as I need an option > -Xconversiontimeout in order to build anything. > > Best Regards, > Andreas Meyer > > List: http://www.antlr.org/mailman/listinfo/antlr-interest > Unsubscribe: > http://www.antlr.org/mailman/options/antlr-interest/your-email-address > 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 -~----------~----~----~----~------~----~------~--~---
