From: Andrea Arcangeli <andrea@suse.de>
To: Rik van Riel <riel@conectiva.com.br>
Cc: Ulrich Drepper <drepper@cygnus.com>,
"linux-kernel@vger.kernel.or" <linux-kernel@vger.kernel.org>
Subject: Re: 2.2.18 signal.h
Date: Fri, 15 Dec 2000 21:22:19 +0100 [thread overview]
Message-ID: <20001215212219.K17781@inspiron.random> (raw)
In-Reply-To: <20001215205721.I17781@inspiron.random> <Pine.LNX.4.21.0012151808540.3596-100000@duckman.distro.conectiva>
In-Reply-To: <Pine.LNX.4.21.0012151808540.3596-100000@duckman.distro.conectiva>; from riel@conectiva.com.br on Fri, Dec 15, 2000 at 06:09:16PM -0200
On Fri, Dec 15, 2000 at 06:09:16PM -0200, Rik van Riel wrote:
> On Fri, 15 Dec 2000, Andrea Arcangeli wrote:
>
> > And yes I can see that the whole point of the change is that
> > they want to also forbids this:
> >
> > x()
> > {
> > goto out;
> > out:
> > }
> >
> > and I dislike not being allowed to do the above as well infact ;).
>
> What's wrong with the - more readable - `break;' ?
You meant "return" of course as you can't put a break there (there's no loop).
`return' doesn't define the fast path (but ok it's a minor issue and
I think latest gcc can use some stuff to define fast paths).
In general all I'm saying is that they don't want a label before the end of a
compound statement and that's a not interesting requirement IMHO that will just
force people to use one additional "suprious" `;' after the last label. It
doesn't make the code more readable and it doesn't give any advantage other
than maybe having simplified some formal language definition.
Andrea
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-15 20:53 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-15 16:29 2.2.18 signal.h Mike Black
2000-12-15 16:56 ` Andrea Arcangeli
2000-12-15 17:07 ` Richard B. Johnson
2000-12-15 17:43 ` Andrea Arcangeli
2000-12-15 17:59 ` Franz Sirl
2000-12-15 18:34 ` Richard B. Johnson
2000-12-15 18:50 ` Alan Cox
2000-12-15 19:06 ` Horst von Brand
2000-12-15 20:15 ` Michael Meissner
2000-12-15 18:54 ` Andrea Arcangeli
2000-12-15 19:18 ` Ulrich Drepper
2000-12-15 19:57 ` Andrea Arcangeli
2000-12-15 20:09 ` Rik van Riel
2000-12-15 20:22 ` Andrea Arcangeli [this message]
2000-12-16 7:53 ` Anuradha Ratnaweera
2000-12-16 13:52 ` Andrea Arcangeli
2000-12-19 16:53 ` Michael Meissner
2000-12-15 19:55 ` Rik van Riel
2000-12-15 20:14 ` Andrea Arcangeli
2000-12-21 18:18 ` Thomas Dodd
2001-01-02 16:55 ` Andrea Arcangeli
2000-12-15 20:31 ` Michael Meissner
2000-12-17 5:27 ` Albert D. Cahalan
2000-12-15 21:56 Jesse Pollard
2000-12-15 22:22 ` Andrea Arcangeli
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=20001215212219.K17781@inspiron.random \
--to=andrea@suse.de \
--cc=drepper@cygnus.com \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
/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 NNTP newsgroup(s).