From: David Carlton <carlton@math.stanford.edu>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb-patches@sources.redhat.com, muller@sources.redhat.com,
bemis <bemis@iol.unh.edu>, clp <clp@iol.unh.edu>
Subject: Re: [rfa] rename p-exp.y's TRUE/FALSE
Date: Mon, 09 Dec 2002 13:15:00 -0000 [thread overview]
Message-ID: <ro1r8cqykzl.fsf@jackfruit.Stanford.EDU> (raw)
In-Reply-To: <3DF500F7.8050807@redhat.com>
On Mon, 09 Dec 2002 15:45:43 -0500, Andrew Cagney <ac131313@redhat.com> said:
> I'll push this up towards BFD, loosing true/false is one changing,
> `helpfully' defining TRUE/FALSE is a second.
Yah. Especially since the defining is silent, so you might not even
be aware of the problem (as those of us using Bison in this situation
weren't):
typedef int bfd_boolean;
#undef FALSE
#undef TRUE
#define FALSE 0
#define TRUE 1
Oh, for a world without #define...
> (yes, approved)
Thanks, committed.
David Carlton
carlton@math.stanford.edu
next prev parent reply other threads:[~2002-12-09 20:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3DF217D9.57B25A10@iol.unh.edu>
2002-12-09 12:45 ` David Carlton
2002-12-09 12:51 ` Andrew Cagney
2002-12-09 13:15 ` David Carlton [this message]
2002-12-10 7:46 ` Pierre Muller
2002-12-10 8:04 ` Andrew Cagney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ro1r8cqykzl.fsf@jackfruit.Stanford.EDU \
--to=carlton@math.stanford.edu \
--cc=ac131313@redhat.com \
--cc=bemis@iol.unh.edu \
--cc=clp@iol.unh.edu \
--cc=gdb-patches@sources.redhat.com \
--cc=muller@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox