public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Marco C. Mason" <mason@ntr.net>
To: Linux-kernel@vger.kernel.org
Subject: Re: [Patch] 2.5.27 sysctl
Date: Tue, 23 Jul 2002 22:21:59 -0400	[thread overview]
Message-ID: <3D3E0F47.59CA2640@ntr.net> (raw)

> > This is making the sysctl code acutally be written in C.
> > It wasn't mostly due to georgeous ommitted size array "forward
> > declarations". As a side effect it makes the table structure easier
to
> > deduce.

<snip>

> The comma changes are gratuitous, as pure ANSI C explicitly allows
such
> constructs. (It was intended to simplify automatic code generation, as

> well as for programmer ease to automatically deal with initializer
> lists.)

> >From the grammar section of the 2nd edition (ca. 1988) of K&R:
>        initializer:
>                assignment-expression
>                { initializer-list }
>                { initializer-list , }
>
> ...where initializer list is what one would expect.

Yeah, it's hard to see it as an "extension" when my copy of K&R (1978)
shows the same thing...

--marco



             reply	other threads:[~2002-07-24  2:12 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-24  2:21 Marco C. Mason [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-07-22 16:56 [PATCH] 2.5.27 sysctl Ray Lee
2002-07-20 19:22 Linux-2.5.27 Linus Torvalds
2002-07-22 10:42 ` [PATCH] 2.5.27 sysctl Marcin Dalecki
2002-07-22 10:53   ` Christoph Hellwig
2002-07-22 10:56     ` Marcin Dalecki
2002-07-22 11:02       ` Christoph Hellwig
2002-07-22 11:03         ` Marcin Dalecki
2002-07-22 12:51           ` Alexander Viro
2002-07-22 13:02             ` Marcin Dalecki
2002-07-22 11:13       ` Christoph Hellwig
2002-07-22 11:19       ` Dave Jones
2002-07-22 11:19       ` bart
2002-07-22 11:21       ` BALBIR SINGH
2002-07-22 12:30       ` Alan Cox
2002-07-22 11:21         ` Marcin Dalecki
2002-07-22 15:57   ` Daniel Egger

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=3D3E0F47.59CA2640@ntr.net \
    --to=mason@ntr.net \
    --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