I use .g3 for all my V3 grammars, including all the ones in the C# port of the Tool, so I already implemented support for multiple extensions. You can use similar code to offer flexibility to the allowed extensions.
However, in the particular use in the Tool (filtering after graph sorting), I believe the file extension is a poor filter. Don't the command line arguments contain the grammar names you want to process, and you could filter on that? Sam -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Gary R. Van Sickle Sent: Wednesday, March 25, 2009 1:14 AM To: 'ANTLR Interest Mailing List' Subject: [antlr-interest] 3.1.3 only accepts *.g extensions Hi guys, It looks like ANTLR 3.1.3 is only accpeting *.g as the grammar's extension, and silently fails if you have any other extension on your grammar file. This breaks Jim I.'s recommended distinct extensions per parser type documented here: http://www.antlr.org/api/C/buildrec.html. -- Gary R. Van Sickle List: http://www.antlr.org/mailman/listinfo/antlr-interest Unsubscribe: http://www.antlr.org/mailman/options/antlr-interest/your-email-address _______________________________________________ antlr-dev mailing list [email protected] http://www.antlr.org/mailman/listinfo/antlr-dev
