other thing: You are using the CSharp target for your grammar. As it
will be removed in ANTLR 3.2, you should switch to the CSharp2 target,
if you don't have to use .NET 1.1.
Johannes
__ Information from ESET NOD32 Antivirus, version of virus signature
database 3837 (20090208) __
It's hiding the
warning that identifier can match now or later (during statements loop).
Ter
__ Information from ESET NOD32 Antivirus, version of virus signature
database 3837 (20090208) __
The message was checked by ESET NOD32 A
http://gogodate.withsex.com/
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"il-antlr-interest" group.
To post to this group, send email to il-antlr-interest@googlegroups.com
To unsubscribe from this group, send emai
Hi folks,
I'm working on a little DSL, called jiffle, to create raster images
from maths expressions. I build an initial AST from the input jiffle
script, and next use a couple of tree walkers to (1) check for
undefined vars and (2) categorize vars on whether thay depend on pixel
position or not
Thanks Gavin. That seems to have worked :-).
--- On Sun, 2/8/09, Gavin Lambert wrote:
> From: Gavin Lambert
> Subject: Re: [antlr-interest] rebuilding antlr 3.1.1 with ant
> To: carter_ch...@yahoo.com, antlr-inter...@antlr.org
> Date: Sunday, February 8, 2009, 12:02 PM
> At 08:53 9/02/2009,
At 08:53 9/02/2009, Carter Cheng wrote:
>I tried making a slight correction to one of the templates for
tree
>parser building in the C directory to hopefully fix the problem
I
>was having w.r.t. the tree parser not compiling under g++ by
>changing the line:
[...]
>I was hoping to test this
I tried making a slight correction to one of the templates for tree parser
building in the C directory to hopefully fix the problem I was having w.r.t.
the tree parser not compiling under g++ by changing the line:
retval.tree = ADAPTOR->rulePostProcessing(ADAPTOR, root_0);
to
retval.tree = (
Vitaliy schrieb:
...
>
> options
> {
> language = CSharp;
> backtrack=true;
> memoize=true;
> }
One other thing: You are using the CSharp target for your grammar. As it
will be removed in ANTLR 3.2, you should switch to the CSharp2 target,
if you d
Yes, this is a problem with ANTLRWorks 1.2.2. Version 1.2.3 will fix
that. The workaround is to avoid a white space in the path of the
grammar file.
Jean
On Feb 7, 2009, at 2:32 PM, Terence Parr wrote:
> Hi. Yeah, I remember something about spaces in filenames or pathnames
> causing trouble
On Feb 8, 2009, at 2:48 AM, Vitaliy wrote:
> root: statements EOF;
> statements: (statement)+;
> statement : label
> | keyword
> | variable
> ;
>
>
Hi,
I managed to answer my own question by looking through the runtime source. I
will try looking at the generator source next and see if I can make some
modifications to it to workaround the problem I have been having with compiling
tree grammar generated code under g++.
Regards,
Carter.
Sexy eye makeup the call now In web dancer scores show nude dancer
in model show chat in online!
Silence is Sexy joins Mininova, distributing their new album for
freeFashion Week Blog: Sexy eye makeup the call now In web dancer
scores show nude dancer
know I go on about the early starts to the da
Hi all,
I've encountered a very interesting case in which it seems to me that Antlr
simply won't backtrack far enough.
The (very) simplified test case of this issue can be demonstrated by the
following grammar:
grammar TestCase;
options
{
language = CSharp;
back
13 matches
Mail list logo
