public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@suse.de>
To: Franz Sirl <Franz.Sirl-kernel@lauterbach.com>
Cc: "Richard B. Johnson" <root@chaos.analogic.com>,
	Mike Black <mblack@csihq.com>,
	"linux-kernel@vger.kernel.or" <linux-kernel@vger.kernel.org>
Subject: Re: 2.2.18 signal.h
Date: Fri, 15 Dec 2000 19:54:33 +0100	[thread overview]
Message-ID: <20001215195433.G17781@inspiron.random> (raw)
In-Reply-To: <Pine.LNX.3.95.1001215120537.1093A-100000@chaos.analogic.com> <20001215175632.A17781@inspiron.random> <Pine.LNX.3.95.1001215120537.1093A-100000@chaos.analogic.com> <20001215184325.B17781@inspiron.random> <4.3.2.7.2.20001215185622.025f8740@mail.lauterbach.com>
In-Reply-To: <4.3.2.7.2.20001215185622.025f8740@mail.lauterbach.com>; from Franz.Sirl-kernel@lauterbach.com on Fri, Dec 15, 2000 at 06:59:24PM +0100

On Fri, Dec 15, 2000 at 06:59:24PM +0100, Franz Sirl wrote:
> It's required by ISO C, and since that's the standard now, gcc spits out a 
> warning. Just adding a ; is enough and already done for most stuff in 
> 2.4.0-test12.

I'm not complaining gcc folks, I just dislike the new behaviour in general,
it's inconsistent.

This is wrong:

x()
{

	switch (1) {
	case 0:
	case 1:
	case 2:
	case 3:
	}
}

and this is right:

x()
{

	switch (1) {
	case 0:
	case 1:
	case 2:
	case 3:
	;
	}
}

Why am I required to put a `;' only in the last case and not in all
the previous ones? Or maybe gcc-latest is forgetting to complain about
the previous ones ;)

Anyway it's a minor issue, if the standard says so we'll live with it.

(and it's also getting offtopic...)

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/

  parent reply	other threads:[~2000-12-15 19:25 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 [this message]
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
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=20001215195433.G17781@inspiron.random \
    --to=andrea@suse.de \
    --cc=Franz.Sirl-kernel@lauterbach.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mblack@csihq.com \
    --cc=root@chaos.analogic.com \
    /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