From: "Eli Zaretskii" <eliz@gnu.org>
To: Mark Kettenis <kettenis@chello.nl>
Cc: gdb@sources.redhat.com
Subject: Re: Preprocessor symbol style
Date: Sat, 14 Aug 2004 10:40:00 -0000 [thread overview]
Message-ID: <9003-Sat14Aug2004133634+0300-eliz@gnu.org> (raw)
In-Reply-To: <200408132202.i7DM1x5k012167@elgar.kettenis.dyndns.org> (message from Mark Kettenis on Sat, 14 Aug 2004 00:02:00 +0200 (CEST))
> Date: Sat, 14 Aug 2004 00:02:00 +0200 (CEST)
> From: Mark Kettenis <kettenis@chello.nl>
>
> #ifdef HAVE_FOO_H
> # include <foo.h>
> #else
> # ifdef HAVE_BAR_H
> # include <bar.h>
> # ifndef HAVE_FOOBAR
> # define FOOBAR FOO(BAR)
> # endif
> # endif
> #endif
>
> This makes it much easier to see how the #if's and #endif's balance.
>
> Can we please adopt the second style for GDB?
I agree that the second style is more readable.
next prev parent reply other threads:[~2004-08-14 10:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-13 22:02 Mark Kettenis
2004-08-13 22:13 ` Daniel Jacobowitz
2004-08-14 10:40 ` Eli Zaretskii [this message]
2004-08-16 18:58 ` Kevin Buettner
2004-08-16 19:33 ` Michael Chastain
2004-08-24 20:25 ` 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=9003-Sat14Aug2004133634+0300-eliz@gnu.org \
--to=eliz@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=kettenis@chello.nl \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).