public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/50134] -Wmissing-prototypes doesn't work for C++
Date: Fri, 30 Sep 2011 07:47:00 -0000	[thread overview]
Message-ID: <bug-50134-4-tYGYpSjMJ2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-50134-4@http.gcc.gnu.org/bugzilla/>

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

Manuel López-Ibáñez <manu at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |manu at gcc dot gnu.org

--- Comment #3 from Manuel López-Ibáñez <manu at gcc dot gnu.org> 2011-09-30 06:54:59 UTC ---
What is the difference between Wmissing-prototypes and Wmissing-declarations?

 -Wmissing-prototypes (C and Objective-C only)
           Warn if a global function is defined without a previous prototype
declaration.  This warning is issued even if the definition itself provides a
prototype.  The aim is to detect global functions that fail to be declared in
header files.

       -Wmissing-declarations
           Warn if a global function is defined without a previous declaration.
 Do so even if the definition itself provides a prototype.  Use this option to
detect global functions that are not declared in header files.  In C++, no
warnings are issued
           for function templates, or for inline functions, or for functions in
anonymous namespaces.


They seem exactly the same thing!


  parent reply	other threads:[~2011-09-30  6:55 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-19 22:17 [Bug c++/50134] New: " hjl.tools at gmail dot com
2011-08-20 10:44 ` [Bug c++/50134] " schwab@linux-m68k.org
2011-09-30  5:59 ` paolo.carlini at oracle dot com
2011-09-30  7:47 ` manu at gcc dot gnu.org [this message]
2011-09-30  8:05 ` manu at gcc dot gnu.org
2011-09-30  8:58 ` redi at gcc dot gnu.org
2011-09-30 14:31 ` joseph at codesourcery dot com
2011-09-30 14:39 ` redi at gcc dot gnu.org
2012-05-15 12:05 ` manu at gcc dot gnu.org
2012-05-15 12:24 ` manu at gcc dot gnu.org
2012-05-15 12:31 ` manu at gcc dot gnu.org
2012-05-24 15:31 ` paolo.carlini at oracle dot com
2012-05-24 19:05 ` manu at gcc dot gnu.org
2012-05-28 21:48 ` paolo.carlini at oracle dot com
2012-05-28 22:09 ` redi at gcc dot gnu.org
2012-05-30 18:58 ` steven at gcc dot gnu.org
2012-05-30 19:08 ` manu at gcc dot gnu.org
2012-06-01  0:39 ` redi at gcc dot gnu.org
2012-06-01  8:47 ` redi at gcc dot gnu.org
2012-06-01  9:40 ` redi at gcc dot gnu.org
2012-06-01 12:39 ` paolo.carlini at oracle dot com

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=bug-50134-4-tYGYpSjMJ2@http.gcc.gnu.org/bugzilla/ \
    --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).