|Ada95 to Ada2005 parser - currently using lex/yacc - problem with Unic email@example.com (2006-12-21)|
|Re: Ada95 to Ada2005 parser - currently using lex/yacc - problem with firstname.lastname@example.org (2006-12-22)|
|Re: Ada95 to Ada2005 parser - currently using lex/yacc - problem with email@example.com (Tommy Nordgren) (2007-03-08)|
|Re: Ada95 to Ada2005 parser - currently using lex/yacc - problem with firstname.lastname@example.org (Tom Copeland) (2007-03-16)|
|Date:||21 Dec 2006 10:33:07 -0500|
|Posted-Date:||21 Dec 2006 10:33:07 EST|
I have a tool that parses Ada95 code and am investigating the
possibilty of updating it to support Ada2005.
The biggest problem I am having at the moment is working out how to
cope with Unicode characters. I currently have a lex/yacc grammar
from which a C parser is generated. I've seen various suggestions on
parser generators that support Unicode, but I don't really know the
way I should proceed. Unfortunately I have fairly little experience
of these things.
In particular, is it going to be at all viable to reuse my exising
lex/yacc grammar with a tool that supports Unicode - before upgrading
the grammar to support Ada2005?
Perhaps another option may be to start afresh with a new tool but
reuse my existing actions?
Or do I need to start from scratch completely? Are there any similar
tools out there for which I can get an Ada2005 grammar, or should I be
considering an ASIS approach (whenever ASIS2005 arrives, that is).
Lots of questions.... any help on this much appreciated.
[The character set issues happen in the lexer which lex generates. A
yacc parser sees only tokens. The question of unicode lexers has come
up frequently over the past decade. See for example
Return to the
Search the comp.compilers archives again.