public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: Jamie Lokier <jamie@shareable.org>
Cc: gcc@gcc.gnu.org
Subject: Re: Documentation bug for __builtin_choose_expr
Date: Mon, 22 Nov 2004 15:02:00 -0000	[thread overview]
Message-ID: <jeu0rix7sx.fsf@sykes.suse.de> (raw)
In-Reply-To: <20041122131946.GA2893@mail.shareable.org> (Jamie Lokier's message of "Mon, 22 Nov 2004 13:19:46 +0000")

Jamie Lokier <jamie@shareable.org> writes:

>      This built-in function is analogous to the `? :' operator in C,
>      except that the expression returned has its type unaltered by
>      promotion rules.  Unlike most built-in functions, but like the
>      `? :' operator, this built-in function does not evaluate the
>      expression that was not chosen.  For example, if CONST_EXP
>      evaluates to true, EXP2 is not evaluated even if it has
>      side-effects.

IMHO, "but like the `? :' operator" could be removed without any negative
impact (anyone who doesn't know how the ?: operator should not look at
builtins either :-) ).

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

  reply	other threads:[~2004-11-22 14:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-22  8:06 Jamie Lokier
2004-11-22 10:41 ` Joseph S. Myers
2004-11-22 10:42   ` Jamie Lokier
2004-11-22 12:21 ` Andreas Schwab
2004-11-22 14:44   ` Jamie Lokier
2004-11-22 15:02     ` Andreas Schwab [this message]
2004-11-22 18:58       ` Robert Dewar
2004-11-22 20:45 ` Kai Henningsen

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=jeu0rix7sx.fsf@sykes.suse.de \
    --to=schwab@suse.de \
    --cc=gcc@gcc.gnu.org \
    --cc=jamie@shareable.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).