From: Segher Boessenkool <segher@kernel.crashing.org>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: "Robert P. J. Day" <rpjday@mindspring.com>,
trivial@kernel.org, Randy Dunlap <randy.dunlap@oracle.com>,
Muli Ben-Yehuda <muli@il.ibm.com>,
Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Documentation: Explain a second alternative for multi-line macros.
Date: Mon, 1 Jan 2007 18:51:05 +0100 [thread overview]
Message-ID: <fb88b3708d2228b345fe68a5a207d069@kernel.crashing.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0701011635420.24520@yvahk01.tjqt.qr>
> If people want to return something from a ({ }) construct, they should
> do it
> explicitly, e.g.
>
> #define setcc(cc) ({ \
> partial_status &= ~(SW_C0|SW_C1|SW_C2|SW_C3); \
> partial_status |= (cc) & (SW_C0|SW_C1|SW_C2|SW_C3); \
> partial_status; \
> })
No, they generally should use an inline function instead.
Segher
next prev parent reply other threads:[~2007-01-01 17:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-31 19:32 [PATCH] Documentation: Explain a second alternative for multi-line macros Robert P. J. Day
2006-12-31 19:45 ` Muli Ben-Yehuda
2006-12-31 19:49 ` Robert P. J. Day
2006-12-31 20:09 ` Muli Ben-Yehuda
2006-12-31 20:03 ` Randy Dunlap
2006-12-31 20:13 ` Robert P. J. Day
2007-01-01 2:40 ` Segher Boessenkool
2007-01-01 3:23 ` Randy Dunlap
2007-01-01 4:31 ` Segher Boessenkool
2007-01-01 4:30 ` Randy Dunlap
2007-01-01 15:37 ` Jan Engelhardt
2007-01-01 17:51 ` Segher Boessenkool [this message]
2007-01-01 19:11 ` Jan Engelhardt
2007-01-01 8:26 ` Robert P. J. Day
2007-01-01 14:20 ` Christoph Hellwig
2007-01-01 14:25 ` Robert P. J. Day
2007-01-01 16:14 ` Randy Dunlap
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=fb88b3708d2228b345fe68a5a207d069@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=muli@il.ibm.com \
--cc=randy.dunlap@oracle.com \
--cc=rpjday@mindspring.com \
--cc=trivial@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.