My own experience is that island grammars are harder to embed without side
effects than I expected. YMMV. In the case of compiler directives I find a
two-pass solution flexible and easier to get right without unexpected results.
Kyle
--Original Message--
From: Andrzej
Sender: antlr-i
Congrats! Time to go read release notes and maybe update my grammars. :)
--Original Message--
From: Terence Parr
Sender: antlr-interest-boun...@antlr.org
To: ANTLR Interest
Cc: ANTLR-dev Dev
Subject: [antlr-interest] ANTLR v3.3 released!
Sent: Nov 29, 2010 8:18 PM
ANTLR 3.3 is out! Get i
I'm on vs2008 for antlr work, so I cannot claim authority but I do deal with
mixed libs every day between multiple releases of vs. Jim Idle knows his code
of course. So your vs2005 code will link fine with antlr built with vs2008 but
the former and latter each use their respective versions of
I believe you have two options. You might prefer to recompile the antlr
runtime DLL with vs2005 If your goal is minimizing dependencies. Alternatively
you could just drop the redistributable C runtime from vs2008 into your
packaging. Unfortunately there's quite a bit of confusion on this poi
Way cool! Just curious...is the modal state variable automatically accessible
to the parser? Perhaps on a subchannel synced with the token stream? Sorry to
be tuning in late...always interested in new paths to semiosis. :)
Anyway...I need to take a look at girhub and think up a fun use.
K
Yep. Pretty complex. I don't have answers but as a user I concur that antlr
lexers have become perhaps a bit unwieldy and this probably gives the
maintainers of the existing targets grief, to say nothing of the impact on new
targets.
I understand the appeal of eliminating codegen for lexers
I do not understand what I perceive between the lines as reticence toward lexer
states. Perhaps states seem "clunky" to some folks. States are elegant -- or
at least clean -- to me, provided the state stack frames are strictly scoped by
design. If communication across frames is allowed via a
Even though empty alts are not the OPs problem...this seems like something
which antlr could preempt with a stern warning at grammar generation time. Or
is there ever a legitimate reason to let it pass?
Sent from my Verizon Wireless BlackBerry
-Original Message-
From: "Jim Idle"
Dat
Surprised to see none of the expected flood of appreciation for this
development, I conclude that I'm not the only one who wasn't watching the wire
today. This is a *very* welcome development! Though all my struggles with
ANTLR ultimately point to my own limitations, this kind of error-reporti
Gavin,
Of your three ideas ...two equivalents in one post and a third more powerful
one in this post ... I currently like the second equivalent from the first
post...viz ~=> for two reasons. First I think your third form is so powerful
as to encourage abuse and expose a lot of strange edge-cas
Regarding the wiki page by the same subject... I'm clearly no expert in the
implementation guts but moving software stack seems like it could have a couple
more benefits in addition to the ones you wrote about. The improved
"separation of concerns" would make it easier (at least for me!) to fol
Don't do it on my account, but I think I would use it because it looks much
more transparent and maintainable. As a new and occasional user, my biggest
challenge is getting my head back in the game after some time away from the
code. This would help.
Kyle
Sent from my Verizon Wireless Black
ROTFL! Thanks for calling it as you see it. I feel a little less naïve now,
knowing that you have "issues" with debugging. Thanks for the nice example too!
Kyle
Sent from my Verizon Wireless BlackBerry
-Original Message-
From: Terence Parr
Date: Tue, 26 Jan 2010 14:57:40
To: antlr
You probably want to make ANY_CHAR a lexer fragment so that it does not consume
input except as part of a larger rule which calls it. Or maybe I missed your
intent.
Kyle
--Original Message--
From: Michael C. Starkie
Sender: ANTLR
To: antlr-interest@antlr.org
Subject: [antlr-interest] Sy
Michael... I feel pity for you if have to parse F77. You're going to run into
a few problems harder to solve/avoid than this. So if you're just going to
discard comments anyway... I suggest you prefilter your input with a tool like
'sed' to strip fixed format comments. Then you can get on wi
Thanks, Gavin. Sorry to top-post, but I think it might be clearer than
multiply interspersed remarks.
I think you understood my logic. If anyone is unclear, it's me.
I take your point about what the debugger already does, which invites the
question 'why does the interp need to be distinc
Hi,
This question is so rudimentary that I am almost embarrassed to ask. But since I almost never try to use ANTLRWorks for my parsers, I'll risk injuring my pride in exchange for learning something.
If I paste the Expr.g *verbatim* from
http://www.antlr.org/works/help/tutorial/content/Expr.
FYI. If anyone is maintaining the info at
http://www.antlr.org/works/help/tutorial/howtorun.html, the last sentence on the
page may be out of date.
I've been using OpenJDL/IcedTea 1.6.x with no problems that I'm aware of.
signature.asc
Description: OpenPGP digital signature
List: http://
18 matches
Mail list logo
