From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Bernd Eckenfels <ecki@lina.inka.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: beware of dead string constants
Date: Thu, 23 Nov 2000 18:39:25 -0500 [thread overview]
Message-ID: <3A1DAAAD.28786302@mandrakesoft.com> (raw)
In-Reply-To: <E13z5nt-0007ig-00@calista.inka.de>
Bernd Eckenfels wrote:
>
> In article <14874.25691.629724.306563@wire.cadcamlab.org> you wrote:
> > This is mostly a heads-up to say that in this regard gcc is not ready
> > for prime time, so we really can't get away with using if() as an ifdef
> > yet, at least not without penalty.
>
> Humm.. whats the Advantage of this?
Advantage of what?
If you mean preferring 'if ()' over 'ifdef'... Linus. :) And I agree
with him: code looks -much- more clean without ifdefs. And the
compiler should be smart enough to completely eliminate code inside an
'if (0)' code block.
Jeff
--
Jeff Garzik |
Building 1024 | The chief enemy of creativity is "good" sense
MandrakeSoft | -- Picasso
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-24 0:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-23 23:29 beware of dead string constants Bernd Eckenfels
2000-11-23 23:39 ` Jeff Garzik [this message]
2000-11-24 3:36 ` Peter Samuelson
2000-11-24 4:15 ` Chris Wedgwood
-- strict thread matches above, loose matches on Subject: below --
2000-11-26 14:29 Bernd Eckenfels
2000-11-22 18:48 Michael Elizabeth Chastain
2000-11-23 13:06 ` Werner Almesberger
2000-11-21 12:02 Peter Samuelson
2000-11-21 12:13 ` Jakub Jelinek
2000-11-21 12:24 ` Peter Samuelson
2000-11-21 20:51 ` J . A . Magallon
2000-11-22 1:14 ` Peter Samuelson
2000-11-22 8:27 ` Urban Widmark
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=3A1DAAAD.28786302@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=ecki@lina.inka.de \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.