[antlr-interest] stuff I don't like about ANTLR 2.x

[Anthony Youngman]

I *think* that gcc allows you to specifically disable certain warnings -
along the lines of "warn everything except warning number 82". I suspect
that when I get things working the way I want, my screen will explode in
ambiguity warnings! The problem is that there might be one warning I
really need to see, and I miss it in the screeds of ambiguity crap I
can't suppress.

I'd suggest that you allocate numbers to all your warnings (you probably
do that already :-) and then print your warnings via a call to a central
routine. Then have some way of telling that routine that, if it's called
for warning(s) x, it should return without doing anything.

Cheers,
Wol 

-----Original Message-----
From: mzukowski at yci.com [mailto:mzukowski at yci.com] 
Sent: 08 March 2004 17:55
To: antlr-interest at yahoogroups.com
Subject: RE: [antlr-interest] stuff I don't like about ANTLR 2.x

I would like a better way to manage all the warnings.  I don't
particularly
like the warnWhenAmbig=false flag.  For one it doesn't work for all the
cases I want it for. 

I think a companion tool could be better at annotating error messages
and
presenting new ones/hiding old ones, etc.  

An ANTLR Cookbook would be quite handy too, and could be built on top of
the
existing examples, and my C grammar :)

Of course there's a slew of tree things but Loring's got that covered
from
the design cabal.

Interactive parsers are not so fun with ANTLR 2.

I would like to be able to trace a Token all the way back to file
offsets so
I could modify files in place, not have to regenerate them entirely.
That's
not so easy with Unicode.

Monty



-----Original Message-----
From: Terence Parr [mailto:parrt at cs.usfca.edu] 
Sent: Saturday, March 06, 2004 12:05 PM
To: antlr-interest at yahoogroups.com
Subject: [antlr-interest] stuff I don't like about ANTLR 2.x

Folks,

In preparation for the ANTLR 3.0 whitepaper, I need to start writing 
down everything that annoys me about ANTLR 2.0.  I have started another 
"blog" document:

http://www.antlr.org/blog/antlr3/antlr2.bashing.tml

Feel free to send in your pet peeves to me or to this list.  I will try 
to add to this file.

I can hear John Mitchell now: "predicate hoisting!" ;)

Terence
--
Professor Comp. Sci., University of San Francisco
Creator, ANTLR Parser Generator, http://www.antlr.org
Cofounder, http://www.jguru.com
Cofounder, http://www.knowspam.net enjoy email again!
Cofounder, http://www.peerscope.com pure link sharing





 
Yahoo! Groups Links



 


 
Yahoo! Groups Links



 





***********************************************************************************

This transmission is intended for the named recipient only. It may contain private and confidential information. If this has come to you in error you must not act on anything disclosed in it, nor must you copy it, modify it, disseminate it in any way, or show it to anyone. Please e-mail the sender to inform us of the transmission error or telephone ECA International immediately and delete the e-mail from your information system.

Telephone numbers for ECA International offices are: Sydney +61 (0)2 9911 7799, Hong Kong + 852 2121 2388, London +44 (0)20 7351 5000 and New York +1 212 582 2333.

***********************************************************************************



 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
     http://groups.yahoo.com/group/antlr-interest/

<*> To unsubscribe from this group, send an email to:
     antlr-interest-unsubscribe at yahoogroups.com

<*> Your use of Yahoo! Groups is subject to:
     http://docs.yahoo.com/info/terms/