From: Roman Zippel <zippel@linux-m68k.org>
To: Tom Rini <trini@kernel.crashing.org>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: small cleanup
Date: Thu, 01 Nov 2001 00:23:06 +0100 [thread overview]
Message-ID: <3BE087DA.8F9ED9CC@linux-m68k.org> (raw)
In-Reply-To: 20011031155335.A20613@cpe-24-221-152-185.az.sprintbbd.net
Hi,
Tom Rini wrote:
> I will when I get a moment.. :) But #ifndef __FOO__ #define __FOO__
> #ifdef __BAR__ ... #endif /* __BAR__ */ #endif /* __FOO__ */ works
> better than checking for __BAR__ first?
IMO yes: "If a subsequent `#include' specifies the same file, and the
macro in the `#ifndef' is already defined, then the file is entirely
skipped, without even reading it."
bye, Roman
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-10-31 23:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-31 1:44 small cleanup Roman Zippel
2001-10-31 2:08 ` Tom Rini
2001-10-31 10:22 ` Roman Zippel
2001-10-31 15:42 ` Tom Rini
2001-10-31 19:49 ` Roman Zippel
2001-10-31 22:53 ` Tom Rini
2001-10-31 23:23 ` Roman Zippel [this message]
2001-11-01 11:19 ` Geert Uytterhoeven
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=3BE087DA.8F9ED9CC@linux-m68k.org \
--to=zippel@linux-m68k.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=trini@kernel.crashing.org \
/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 NNTP newsgroup(s).