public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bangerth@dealii.org
To: austern@apple.com, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	nobody@gcc.gnu.org
Subject: Re: c++/8076: -Wmissing-declarations is C-only, conflicts with documentation
Date: Thu, 15 May 2003 05:42:00 -0000	[thread overview]
Message-ID: <20030515054213.19261.qmail@sources.redhat.com> (raw)

Synopsis: -Wmissing-declarations is C-only, conflicts with documentation

State-Changed-From-To: open->closed
State-Changed-By: bangerth
State-Changed-When: Thu May 15 05:42:13 2003
State-Changed-Why:
    The C-only part has been fixed. Matt, I agree with Gaby that
    the -Wmissing-declarations is not very useful, since, for 
    example, most of the STL is implemented in header files (using
    inline functions) that have no prior declaration.
    
    Regarding the other issue (misdeclaration): there's not
    much you can do in C++, because you can overload. So if
    a declaration doesn't match a definition or another
    declaration for the same name, that's not an error, but
    just declares a second function. There may be something
    that I don't see, but I think I would prefer if we had
    a separate bug report for this if you feel that there's
    something missing.
    
    Thanks
      Wolfgang

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8076


             reply	other threads:[~2003-05-15  5:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-15  5:42 bangerth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-10-15  4:36 Gabriel Dos Reis
2002-10-14 15:16 Matt Austern
2002-09-28  8:36 Gabriel Dos Reis
2002-09-27 16:46 austern

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=20030515054213.19261.qmail@sources.redhat.com \
    --to=bangerth@dealii.org \
    --cc=austern@apple.com \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).