From: Rob Browning <rlb@defaultvalue.org>
Cc: guile-devel@gnu.org
Subject: Re: #if vs #ifdef
Date: Thu, 27 Mar 2003 09:56:05 -0600 [thread overview]
Message-ID: <871y0sg5wq.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <20030327074805.1352f925.dsmith@altustech.com> ("Dale P. Smith"'s message of "Thu, 27 Mar 2003 07:48:05 -0500")
"Dale P. Smith" <dsmith@altustech.com> writes:
> I don't understand how it better for the compiler though. I would think
> using #if's effectively edits the code out of the way before the
> compiler has a chance to look at it. Using if (..) gives the compiler
> useless work to do. How is theis better?
I think the main argument is that it allows the compiler to check all
the code paths on every compile.
--
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2003-03-27 15:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-27 6:18 #if vs #ifdef Rob Browning
2003-03-27 9:43 ` tomas
2003-03-27 12:48 ` Dale P. Smith
2003-03-27 15:26 ` tomas
2003-03-27 15:08 ` Dale P. Smith
2003-03-27 15:56 ` Rob Browning [this message]
2003-03-27 15:13 ` Marius Vollmer
2003-03-27 19:47 ` Rob Browning
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871y0sg5wq.fsf@raven.i.defaultvalue.org \
--to=rlb@defaultvalue.org \
--cc=guile-devel@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).