Hi Seref and Erik, The grammar published on openEHR by Ocean Informatics was what we used with a proprietary third party tool. If people have converted the grammar to work with more standard parsing tools and want to post it to the AQL wiki page for others to use then we too can test it with our tool and if successful can deprecate the original.
Heath On 05/01/2012 9:31 PM, "Seref Arikan" <serefarikan at kurumsalteknoloji.com> wrote: > Thanks Erik, > AntlrWorks is nice, but it has a problem of slowing down for some reason, > even if the grammar is not that big. Appears to be a known issue, but the > latest version still has this behaviour. Still beats anything else out > there though. > > For me, ANTLR's main advantage is its infrastructure to support multiple > target languages. I've used JavaCC a long time ago, and I don't think it is > inferior to Antlr, though Antlr has a bit of a learning curve. > > I'm working on the refactoring of the existing grammar via elimination of > left recursions, but my point is pretty much the same with yours; moving > grammars to Antlr would help different groups develop parsers/tools easier. > I've asked the original question to see if people did the actual work of > eliminating recursions and basically making grammar LL compatible, and > based on the responses I can see that they have. > > This is good news, since it means we may be able to build a community > around Antlr based implementations. Good to hear that you'll be putting > something out soon, I'll try to do the same ;) > > Regards > Seref > > > On Thu, Jan 5, 2012 at 10:12 AM, Erik Sundvall <erik.sundvall at liu.se>wrote: > >> Hi! >> >> We implemented an AQL parser using JavaCC. My colleague Mikael Nystr?m >> made some transformations to make the published AQL grammar work in JavaCC. >> Mikael is on vacation right now, but I'm sure he does not mind sharing his >> experiences once he gets back. >> >> I do think it would be interesting to switch to ANTLR sooner or later in >> order to share efforts between projects with different >> implementation/target-languages and because the ANTLRWorks environment >> http://www.antlr.org/works/index.html looks promising compared to the >> pretty bad JavaCC-plugin in e.g. Eclipse. >> >> Our parser (and thus also the modified grammar) will soon be open sourced >> so you are free to use it. So if you are not in an extreme hurry I'd >> suggest using or getting inspiration from what we have already done. >> >> Best regards, >> Erik Sundvall >> erik.sundvall at liu.se http://www.imt.liu.se/~erisu/ Tel: +46-13-286733 >> >> >> >> On Wed, Jan 4, 2012 at 16:37, Seref Arikan < >> serefarikan at kurumsalteknoloji.com> wrote: >> >>> Greetings, >>> The AQL grammar from the wiki has direct and indirect left recursion. >>> Which means without changes in the grammar, LL parser generators (both >>> JavaCC and Anltr) can't generate parsers for this grammar. >>> >>> I'm curious if anybody has refactored this grammar for LL parser >>> generators. Shinji? Your latest release includes an AQL parser does not it? >>> Could you please share your method? I can always look at the code, but >>> you'd probably save me time :) >>> >>> I'm interested in experiences of others too. >>> >>> >>> Kind regards >>> Seref >>> >> >> _______________________________________________ >> openEHR-technical mailing list >> openEHR-technical at openehr.org >> http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical >> >> > > _______________________________________________ > openEHR-technical mailing list > openEHR-technical at openehr.org > http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20120106/12ee3e66/attachment.html>
