[gnu.g++.bug] 'catch' as keyword considered unfortunate

tiemann@LURCH.STANFORD.EDU (Michael Tiemann) (12/09/89)

C++ 2.0 reserves `catch', I'm just following along.  I disable words
reserved for the experimental GNU exception handling code by default.
Look in cplus-lex.c for UNSET_RESERVED_WORD for how to do this easily.
Handle `catch' there, and you are set.

Michael

dld@JMW.LARCH.CS.CMU.EDU (David Detlefs) (12/09/89)

Michael --

Could I register a request that some future release of G++ have a mode
in which (at least) the exception handling mechanism is disabled?  I
have to compile code I don't own (Mach include files) that happen to
use 'catch' as a structure field tag.  G++ can't compile these include
files; I have to go through some hassle to get things to work.  I
can't really see myself going to the people in charge of these files
and saying, "Uh, could you please not use 'catch' as a name?"  I think
they would have a legitimate objection if they said, well, this is a
include file for C, and we're willing to some work to make it C++, but
if G++ is going off and defining a new language...  (Note that I'm not
accusing anyone of this, just proposing it as a somewhat
understandable objection.)

In more generality: it would be nice if there were an AT&T
compatibility mode.

For what it's worth...

Dave