public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@suse.de>
To: Anuradha Ratnaweera <anuradha@gnu.org>
Cc: Ulrich Drepper <drepper@cygnus.com>,
	"linux-kernel@vger.kernel.or" <linux-kernel@vger.kernel.org>
Subject: Re: 2.2.18 signal.h
Date: Sat, 16 Dec 2000 14:52:42 +0100	[thread overview]
Message-ID: <20001216145242.C25150@inspiron.random> (raw)
In-Reply-To: <20001215205721.I17781@inspiron.random> <Pine.LNX.4.21.0012161337220.1433-100000@bee.lk>
In-Reply-To: <Pine.LNX.4.21.0012161337220.1433-100000@bee.lk>; from anuradha@gnu.org on Sat, Dec 16, 2000 at 01:53:50PM +0600

On Sat, Dec 16, 2000 at 01:53:50PM +0600, Anuradha Ratnaweera wrote:
> GCC will complain the absence of a statement after `out1:out2:`, but not
> two complains for `out1' and `out2', because they form a single entity.

I understand the formal specs (the email from Michael is very clear). What I'm
saying is that as the `dummy' statement is redoundant information but you're
requiring us to put it to build a labeled-statement, you could been even more
lazy and not define the labeled-statement as a statement so requiring us to put
a dummy statement after every label. That would been the same kind of issue
we're facing right now (but of course defining a labeled-statement as a
statement and allowing recursion makes the formal specs even simpler so that
probably wouldn't happen that easily).

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/

  reply	other threads:[~2000-12-16 14:23 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
2000-12-16  7:53             ` Anuradha Ratnaweera
2000-12-16 13:52               ` Andrea Arcangeli [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
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=20001216145242.C25150@inspiron.random \
    --to=andrea@suse.de \
    --cc=anuradha@gnu.org \
    --cc=drepper@cygnus.com \
    --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