From: Andi Kleen <ak@suse.de>
To: kuznet@ms2.inr.ac.ru
Cc: rddunlap@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: Linux v2.5.48
Date: 27 Nov 2002 05:57:58 +0100 [thread overview]
Message-ID: <p73lm3ftxrd.fsf@oldwotan.suse.de> (raw)
In-Reply-To: kuznet@ms2.inr.ac.ru's message of "27 Nov 2002 01:49:57 +0100"
kuznet@ms2.inr.ac.ru writes:
> > It would be OK with me not to accept such extensions. :)
>
> One of a few of extensions which does not cause any reaction
> but "it's strange that it was not in KR, apparently it was lost
> due to a buglet in the first parser" :-)
IMHO it's a bit dangerous. It even inspired me to my first gcc
patch, adding a warning for:
bla > 0 ? : somethingelse
(boolean expression as first argument)
returning the boolean value for true which would be always 1. But the real
intention was to return bla. I did this mistake at least twice. After that
I decided to avoid this extension. Unfortunately the gcc guys ignored the patch
to warn for it.
-Andi
next parent reply other threads:[~2002-11-27 4:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.33L2.0211261547450.2873-100000@dragon.pdx.osdl.net.suse.lists.linux.kernel>
[not found] ` <200211270042.DAA19185@sex.inr.ac.ru.suse.lists.linux.kernel>
2002-11-27 4:57 ` Andi Kleen [this message]
2002-11-18 18:30 Linux v2.5.48 Manfred Spraul
2002-11-18 18:59 ` Linus Torvalds
2002-11-18 19:09 ` Manfred Spraul
2002-11-18 19:14 ` Linus Torvalds
2002-11-18 20:57 ` William Lee Irwin III
2002-11-18 21:28 ` Manfred Spraul
-- strict thread matches above, loose matches on Subject: below --
2002-11-18 4:41 Linus Torvalds
2002-11-18 6:57 ` William Lee Irwin III
2002-11-18 7:19 ` William Lee Irwin III
2002-11-18 7:47 ` Martin J. Bligh
2002-11-18 7:55 ` William Lee Irwin III
2002-11-18 9:08 ` Gabor Z. Papp
2002-11-18 12:37 ` Adrian Bunk
2002-11-18 18:33 ` Udo A. Steinberg
2002-11-19 5:13 ` Linus Torvalds
2002-11-26 23:15 ` Adrian Bunk
2002-11-26 23:49 ` Randy.Dunlap
2002-11-27 0:42 ` kuznet
2002-11-27 0:53 ` Adrian Bunk
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=p73lm3ftxrd.fsf@oldwotan.suse.de \
--to=ak@suse.de \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.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.