public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: ebb9@email.byu.edu
To: gcc-gnats@gcc.gnu.org
Subject: libstdc++/3916: Bad example in style docs
Date: Thu, 02 Aug 2001 07:56:00 -0000	[thread overview]
Message-ID: <20010802144341.3302.qmail@sourceware.cygnus.com> (raw)

>Number:         3916
>Category:       libstdc++
>Synopsis:       Bad example in style docs
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          doc-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Aug 02 07:56:01 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     Eric Blake
>Release:        unknown-1.0
>Organization:
>Environment:
N/A
>Description:
There is an invalid trailing comma in the "good" example of Rule 6 of the libc++ style guide, located online at:
http://gcc.gnu.org/onlinedocs/libstdc++/17_intro/C++STYLE

enum { name, }; is not currently legal C++, although it was made legal for C99; and while g++ will compile it without complaint as a common extension, there are compilers, such as aCC on HP-UX 10, that will not.  The corresponding "bad" example in rule 6 is correct.
>How-To-Repeat:
N/A
>Fix:
This is how the web page should appear; I am not in a position to provide the actual patch against the file CVS that the web page is generated from.

   {
     space = _ISspace,
     print = _ISprint,
-    cntrl = _IScntrl,
+    cntrl = _IScntrl  // no comma for last entry
   };
   -NOT-
   enum { space = _ISspace, print = _ISprint, cntrl = _IScntrl };
>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2001-08-02  7:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-02  7:56 ebb9 [this message]
2001-08-24 13:54 pme

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=20010802144341.3302.qmail@sourceware.cygnus.com \
    --to=ebb9@email.byu.edu \
    --cc=gcc-gnats@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).