[il-antlr-interest: 33910] Re: [antlr-interest] StringTemplate 4 Question

2011-09-05 Thread Ben Corne
I'm using ST4.04 and this works for me. I think you want the stringtemplate-inter...@antlr.org mailinglist though. Regards, Ben 2011/9/5 Mark javam...@gmail.com Hiya All. In ST 3 you could point to a directory of templates and then retrieve a templatre instance by it's name via it's name.

[il-antlr-interest: 33617] Re: [antlr-interest] gathering any character until specified char

2011-08-15 Thread Ben Corne
: ( ' ' | '\t' | '\r' | '\n' ) ; Input: Ben Corne , An antlr FAN Parse tree should look like this: authors | 'Ben Corne' | WS | ',' | WS | 'An antlr FAN' Instead I get one that doesn't seem to gather

[il-antlr-interest: 33605] [antlr-interest] Pre parse keyworded function calls into canonical function calls

2011-08-12 Thread Ben Corne
=(~KEYWORD*) ; KEYWORD : ( 'A'..'Z' | 'a'..'z' ) ':' ; do some magic to rewrite foo: x bar: y into foo:bar:(x,y); 2) Run the regular language grammar over the modified input from the first pass. Kind Regards Ben Corne. List: http://www.antlr.org/mailman/listinfo/antlr-interest Unsubscribe: http

[il-antlr-interest: 32480] [antlr-interest] Fragment rules inside parser rules

2011-05-18 Thread Ben Corne
Hello Do I really need to make LKU in the example below a normal token rule or is there a way to get this to work for the input 'foo;' not using literals inside the parser rule or real tokens. grammar Foo; program : (LKU NAME ';')+ ; fragment LKU : '' ; NAME :

[il-antlr-interest: 32466] [antlr-interest] Automatic lists

2011-05-17 Thread Ben Corne
Hi I'm trying to create a rule looking like this: == statement : ( docs+=documentation )* ( def=definition - ^(AGSTATEMENT $docs $def) | tdef=typedefinition - ^(AGSTATEMENT $docs $tdef) | imp=imports - ^(AGSTATEMENT $docs $imp) // TODO: (variable EQL) =

[il-antlr-interest: 32459] [antlr-interest] Fragments for rewrite rules

2011-05-16 Thread Ben Corne
Hi Below an example of me trying to use fragment lexer rules to use in rewrite rules. But when I try this out in the interpreter: - 'test bar', with a fragment rule AGTEST conflicting with reading 'test', doesn't parse - 'foo bar', where no fragmented rule conflicts with reading input, parses I

[il-antlr-interest: 32412] Re: [antlr-interest] Source code level of ANTLRWorks

2011-05-09 Thread Ben Corne
] On Behalf Of Ben Corne Sent: Thursday, May 05, 2011 4:58 AM To: antlr-interest@antlr.org Subject: Re: [antlr-interest] Source code level of ANTLRWorks Here's a screenshot of my antlrworks preferences page + javac info http://igor.rave.org/antlrjavac.png I don't see the option where

[il-antlr-interest: 32382] Re: [antlr-interest] Source code level of ANTLRWorks

2011-05-05 Thread Ben Corne
[mailto:antlr-interest- boun...@antlr.org] On Behalf Of Ben Corne Sent: Wednesday, May 04, 2011 6:56 AM To: antlr-interest@antlr.org Subject: [antlr-interest] Source code level of ANTLRWorks Hi Is there a way to set the source code level of antlrworks? I've checked the preferences pane

[il-antlr-interest: 32365] [antlr-interest] Source code level of ANTLRWorks

2011-05-04 Thread Ben Corne
) [15:47:58] StackString paraphrase = new StackString(); [15:47:58] ^^ [15:47:58] Syntax error, parameterized types are only available if source level is 1.5 Regards Ben Corne List: http://www.antlr.org/mailman/listinfo/antlr-interest Unsubscribe: http

[il-antlr-interest: 32193] [antlr-interest] |! in antlr2

2011-04-14 Thread Ben Corne
I have an antlr2 gramatica which I'm converting to antlr3. Multiple rules make use of the folowing construct: someRule : ! otherexpressions | ! more | ... What is the meaning of ! at the start of a branch? Scrape the entire branch when building an AST? Regards Ben Corne List: http

[il-antlr-interest: 32103] [antlr-interest] Illegal option output

2011-04-06 Thread Ben Corne
Hello Attached is my grammar file. When running antlr over it (with antlridev3 eclipse plugin), it states the following error: ANTLR Parser Generator 3.3 Nov 30, 2010 12:50:56. Using project classpath: Yes. Grammar: /home/bcorne/ATDOC/Documenter/grammar/Documentation.g warning(149):

[il-antlr-interest: 32104] Re: [antlr-interest] Illegal option output

2011-04-06 Thread Ben Corne
I just found out you cannot use ! within lexer rules. It works now. 2011/4/6 Ben Corne ben.co...@gmail.com Hello Attached is my grammar file. When running antlr over it (with antlridev3 eclipse plugin), it states the following error: ANTLR Parser Generator 3.3 Nov 30, 2010 12:50:56

[il-antlr-interest: 31781] [antlr-interest] simple annotation parser

2011-03-10 Thread Ben Corne
Hello I'm trying to parse the examplary lines: example1: //@author Ben Corne example2: //@ this is an example docstring However, when running this in the interpreter window on example 1 or 2, it always seems to cut off the last last part of the letters in the resulting tree: http://igor.rave.org

[il-antlr-interest: 31653] [antlr-interest] ANTLR V3 Comments parsing (and retaining them)

2011-02-27 Thread Ben Corne
I want to create a documentation tool for some language, this involves introducing new syntax which can be ignored by the normal parser, but is taken into account when feeding a program to the documenter-parser. Here's where I started off with: (the language itself is added after I get the