From: Joseph Carter <knghtbrd@debian.org>
To: Bart Trojanowski <bart@jukie.net>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: asm/unistd.h
Date: Thu, 5 Apr 2001 07:26:28 -0700 [thread overview]
Message-ID: <20010405072628.C22001@debian.org> (raw)
In-Reply-To: <A0C675E9DC2CD411A5870040053AEBA0284170@MAINSERVER> <Pine.LNX.4.30.0104050901500.13496-100000@localhost>
In-Reply-To: <Pine.LNX.4.30.0104050901500.13496-100000@localhost>; from bart@jukie.net on Thu, Apr 05, 2001 at 09:06:20AM -0400
[-- Attachment #1: Type: text/plain, Size: 650 bytes --]
On Thu, Apr 05, 2001 at 09:06:20AM -0400, Bart Trojanowski wrote:
> So you ask: "why not just use a { ... } to define a macro". I don't
> remember the case for this but I know it's there. It has to do with a
> complicated if/else structure where a simple {} breaks.
This doesn't follow in my mind. I can't think of a case where a { ... }
would fail, but a do { ... } while (0) would succeed. The former would
also save a few keystrokes.
--
Joseph Carter <knghtbrd@debian.org> Free software developer
// Minor lesson: don't fuck about with something you don't fully understand
-- the dosdoom source code
[-- Attachment #2: Type: application/pgp-signature, Size: 273 bytes --]
next prev parent reply other threads:[~2001-04-05 14:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-05 12:58 asm/unistd.h Sardañons, Eliel
2001-04-05 13:06 ` asm/unistd.h Bart Trojanowski
2001-04-05 13:12 ` asm/unistd.h Tim Waugh
2001-04-05 14:26 ` Joseph Carter [this message]
2001-04-05 14:35 ` asm/unistd.h Bart Trojanowski
2001-04-05 14:35 ` asm/unistd.h Stephen Thomas
2001-04-05 14:45 ` asm/unistd.h Andreas Schwab
2001-04-05 17:38 ` asm/unistd.h J . A . Magallon
2001-04-05 13:07 ` asm/unistd.h David S. Miller
2001-04-05 13:13 ` asm/unistd.h Ben Collins
-- strict thread matches above, loose matches on Subject: below --
2001-04-05 15:23 asm/unistd.h Steve Grubb
2001-04-05 15:41 ` asm/unistd.h Bart Trojanowski
2001-04-05 15:45 ` asm/unistd.h David S. Miller
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=20010405072628.C22001@debian.org \
--to=knghtbrd@debian.org \
--cc=bart@jukie.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox