[il-antlr-interest: 28561] [antlr-interest] required (...)+ loop did not match anything at input 'EOF'

Hello, List! I try to develop a lexer\parser for SIP portocol grammar. But now I have the following error after an attempt to parse INVITE sip:ssedai string: line 1:12 mismatched character 's' expecting 'i' line 1:13 no viable alternative at character 'e' line 1:14 no viable alternative at

[il-antlr-interest: 28563] [antlr-interest] Another JUnit testing framework

Hello, I started working on another JUnit testing framework for ANTLR. Mainly as a mechanism to learn how to write a JUnit testing and, secondarily, to test my grammars in a way that I was comfortable with. It's a great mix of Jeremy D. Frens' assert code from the antlr-

[il-antlr-interest: 28565] [antlr-interest] Overriding rule in imported parser grammar generates a faulty java code with undefined method

Title: Overriding rule in imported parser grammar generates a faulty java code with undefined method Description: Simple extended example from the article about the import introduction: A parser 1 defines a rule that will be override by parser 2 importing parser 1. The combined grammar

[il-antlr-interest: 28566] [antlr-interest] Imported parser grammar importing another grammar produces unsuspected errors

Title: Imported parser grammar importing another grammar produces unsuspected errors Description: The original example from the article about the import introduction: A combined grammar imports a parser grammar importing an other parser grammar. (without overriding) Software:

[il-antlr-interest: 28567] [antlr-interest] Combined grammar importing lexer and parser grammar could not define lexer rules

Title: Combined grammar importing lexer and parser grammar could not define lexer rules Description: A combined grammar with imported lexer and parser grammar is given. In this grammar header rules have to be set for example for package declarations. Software: antlrworks-1.3.1.jar

[il-antlr-interest: 28569] Re: [antlr-interest] Another JUnit testing framework

Alan, Overall your code looks very clean. Do you have any samples that demonstrate usage? (I looked around but your README and docs directories are basically empty :). Thanks. -- Kaleb Pederson Blog - http://kalebpederson.com Twitter - http://twitter.com/kalebpederson On Thursday 22 April

[il-antlr-interest: 28570] Re: [antlr-interest] Another JUnit testing framework

It's in the tests of the it directory: http://github.com/maguro/aunit/blob/master/it/src/test/java/com/toolazydogs/aunit/CMinusTest.java Regards, Alan On Apr 22, 2010, at 11:13 AM, Kaleb Pederson wrote: Alan, Overall your code looks very clean. Do you have any samples that demonstrate

[il-antlr-interest: 28572] [antlr-interest] Coding rule checking for Ada 95

Hum, okay... My problem is : the better I get it running, the better it is for my ass ^^ Now, I'm evaluating the feasibility of a solution : - based on ANTLR and Java target (thanks to Aonix Hibachi eclipse plugin) - with a Scala overlay to get a functionnal approach for all tree

[il-antlr-interest: 28573] [antlr-interest] token not recognized

Hi all, I have defined a token called GEN that can take on various string values. The grammar is below. The token is question is GEN. I'm trying to parse a very simple string conforming to this grammar: Unavailable(LEP). When it sees LEP it complains that it found 'LEP' when it was expecting

[il-antlr-interest: 28574] Re: [antlr-interest] token not recognized

Greetings! On Thu, 2010-04-22 at 12:04 -0800, kumarr wrote: Hi all, I have defined a token called GEN that can take on various string values. The grammar is below. The token is question is GEN. I'm trying to parse a very simple string conforming to this grammar: Unavailable(LEP). When it

[il-antlr-interest: 28575] Re: [antlr-interest] token not recognized

Thanks! I had figured out that putting an _ fixed the problem. Now I know why it did so. Rajesh -Original Message- From: John B. Brodie [mailto:j...@acm.org] Sent: Thursday, April 22, 2010 4:23 PM To: Kumar, Rajesh (Systems) UTRC Cc: antlr-interest@antlr.org Subject: Re: