public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "roland dot illig at gmx dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/17083] New: documentation of "implementation-defined behaviour" is incomplete
Date: Wed, 18 Aug 2004 13:18:00 -0000	[thread overview]
Message-ID: <20040818131804.17083.roland.illig@gmx.de> (raw)

The documentation of the implementation-defined behaviour is incomplete. In some
cases there are only the sentences from the language standards but not a single
word about how it is implemented. There should at least be the word TODO
(better: FIXME) to indicate that there is a sentence missing.

example: chapter 4.1, item 2

C99, J.3#1: ``A conforming implementation is _required_ to document its choice
of behavior in _each_ of the areas listed in this subclause.''

-- 
           Summary: documentation of "implementation-defined behaviour" is
                    incomplete
           Product: gcc
           Version: 3.4.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: other
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: roland dot illig at gmx dot de
                CC: gcc-bugs at gcc dot gnu dot org
 GCC build triplet: n/a
  GCC host triplet: n/a
GCC target triplet: n/a


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17083


             reply	other threads:[~2004-08-18 13:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-18 13:18 roland dot illig at gmx dot de [this message]
2004-08-18 14:03 ` [Bug other/17083] " jsm at polyomino dot org dot uk
2004-08-18 16:59 ` roland dot illig at gmx dot de
2004-08-18 17:02 ` pinskia at gcc dot gnu dot org

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=20040818131804.17083.roland.illig@gmx.de \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).