From: david nicol <whatever@davidnicol.com>
To: Aschwin Marsman <a.marsman@aYniK.com>
Cc: Timothy Miller <miller@techsource.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Coding technique question
Date: 18 Jun 2003 21:16:04 -0500 [thread overview]
Message-ID: <1055988964.1032.25.camel@plaza.davidnicol.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0306162202480.1924-100000@localhost.localdomain>
i-yi-yi.
/*
* Clarity concerning the
* do {
* ...
* } while (0);
* construct!
*/
#define MACRO_BLOCK_BEGIN do {
#define MACRO_BLOCK_END } while (0);
> See the Kernel Newbies FAQ at http://kernelnewbies.org/faq/
> Q: "Why do a lot of #defines in the kernel use do { ... } while(0)? "
>
> Best regards,
>
> Aschwin Marsman
--
David Nicol, independent consultant and contractor
Senator Orrin Hatch rewinds his DVDs
prev parent reply other threads:[~2003-06-19 2:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-16 20:03 Timothy Miller
2003-06-16 19:56 ` Jeff Garzik
2003-06-16 20:05 ` Aschwin Marsman
2003-06-16 20:23 ` Timothy Miller
2003-06-19 2:16 ` david nicol [this message]
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=1055988964.1032.25.camel@plaza.davidnicol.com \
--to=whatever@davidnicol.com \
--cc=a.marsman@aYniK.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miller@techsource.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
all inboxes | Powered by JetHome®