From: Stephen Satchell <satch@fluent-access.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] pedantic code cleanup - am I wasting my time with this?
Date: Tue, 24 Apr 2001 01:25:43 -0700 [thread overview]
Message-ID: <4.3.2.7.2.20010424012505.00b80590@mail.fluent-access.com> (raw)
At 05:58 PM 4/23/01 +0200, you wrote:
>>On Mon, Apr 23, 2001 at 05:26:27PM +0200, Jesper Juhl wrote:
>>>last entry should not have a trailing comma.
>>Sadly not. This isn't a gcc thing: ANSI says that trailing comma is ok (K&R
>>Second edition, A8.7 - pg 218 &219 in my copy)
>
>You are right, I just consulted my own copy, and nothing strictly forbids
>the comma... Sorry about that, I should have been more thorough before
>reporting that one...
From the X3J11 Rationale document, paraphrase: The inclusion of optional
trailing commas is to ease the task of generating code by automatic
programs such as LEX and YACC.
Satch
next reply other threads:[~2001-04-24 8:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-24 8:25 Stephen Satchell [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-04-23 15:26 Jesper Juhl
2001-04-23 15:24 ` Jeff Garzik
2001-04-23 15:37 ` Richard Gooch
2001-04-23 16:23 ` Jesper Juhl
2001-04-23 15:48 ` Sean Hunter
2001-04-23 15:58 ` Jesper Juhl
2001-04-24 4:59 ` Rusty Russell
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=4.3.2.7.2.20010424012505.00b80590@mail.fluent-access.com \
--to=satch@fluent-access.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
all inboxes | Powered by JetHome®