All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rich Baum" <baumr1@coral.indstate.edu>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: "Albert D. Cahalan" <acahalan@cs.uml.edu>,
	acahalanrth@twiddle.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] More compile warning fixes for 2.4.0
Date: Wed, 10 Jan 2001 08:17:11 -0500	[thread overview]
Message-ID: <3A5C1A87.27149.604DC6@localhost> (raw)
In-Reply-To: <20010110032048.B9486@athlon.random>
In-Reply-To: <Pine.LNX.4.10.10101092304410.3414-100000@penguin.transmeta.com>

On 9 Jan 2001, at 23:10, Linus Torvalds wrote:

> 
> 
> On Wed, 10 Jan 2001, Andrea Arcangeli wrote:
> 
> > On Tue, Jan 09, 2001 at 01:31:35PM -0800, Linus Torvalds wrote:
> > > don't have to worry about undocumented extensions etc.
> > 
> > Infact I don't blame gcc maintainers for that, but the standard. Ok, minor
> > issue.
> 
> Yeah, and nothing we can do about it any more.. Oh, well.
> 
> The fact is that the 
> 
> 	case xxx: ;
> 
> syntax is fairly ugly, so I'd prefer the fixup patches to look more like
> 
> 	case xxx:
> 		/* fallthrough */ ;
> 	}
> 
> or something (or maybe just a "break" statement), just so that we don't
> turn the poor C language into line noise (can anybody say "perl" ;)
> 
> I have to say, I think it was Pascal had this "no semicolon needed before
> an 'end'" rule, and I always really hated that. The C statement rules make
> a lo tmore sense, and requiring a statement after a case statement is
> probably a very good requirement from a language standpoint. It's just not
> very pretty - but adding a break or a comment will at least separate out
> the colon and the semi-colon a bit.
> 
> 		Linus
> 
> -
> 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/

I'll redo my patch to use break; and then I'll resend it.
-
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:[~2001-01-10 13:17 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-07  2:40 [PATCH] More compile warning fixes for 2.4.0 Rich Baum
2001-01-07 12:41 ` Paul Gortmaker
2001-01-07 13:17   ` Keith Owens
2001-01-08 19:50 ` Erik Mouw
2001-01-08 20:17   ` Alan Cox
2001-01-09  5:30   ` Richard Henderson
2001-01-09 10:02     ` Albert D. Cahalan
2001-01-09 15:10       ` Richard B. Johnson
2001-01-09 18:51       ` Linus Torvalds
2001-01-09 21:24         ` Albert D. Cahalan
2001-01-09 21:31           ` Linus Torvalds
2001-01-10  2:20             ` Andrea Arcangeli
2001-01-10  7:10               ` Linus Torvalds
2001-01-10 13:17                 ` Rich Baum [this message]
2001-01-10 13:32                 ` Andrea Arcangeli
2001-01-10 16:03                 ` Marco Colombo
2001-01-10 16:52                   ` Alan Shutko
2001-01-10 17:32                     ` Marco Colombo
2001-01-10 17:19                   ` Linus Torvalds
2001-01-10 18:02                     ` Marco Colombo
2001-01-10  1:58         ` Rich Baum
2001-01-09  1:23 ` Rich Baum

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=3A5C1A87.27149.604DC6@localhost \
    --to=baumr1@coral.indstate.edu \
    --cc=acahalan@cs.uml.edu \
    --cc=acahalanrth@twiddle.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=richbaum@acm.org \
    --cc=torvalds@transmeta.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 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.