public inbox for
help / color / mirror / Atom feed
From: Gabriel Dos Reis <>
Subject: Re: c++/8076: -Wmissing-declarations is C-only, conflicts with documentation
Date: Tue, 15 Oct 2002 04:36:00 -0000	[thread overview]
Message-ID: <> (raw)

The following reply was made to PR c++/8076; it has been noted by GNATS.

From: Gabriel Dos Reis <>
To: Matt Austern <>
Subject: Re: c++/8076: -Wmissing-declarations is C-only, conflicts with documentation
Date: 15 Oct 2002 13:27:42 +0200

 Matt Austern <> writes:
 | I understand that the documentation is going to be changed to say
 | that this is a C-only option.  I suggest, however, that changing the
 | documentation doesn't mean we should close this bug; rather, it
 | means we should reclassify this from a bug to a feature request.
 OK, I'll reclassify it.
 | Seems to me that this warning is still useful for C++.  Arguably
 | more useful than in C: in C you'll get an error message from
 |    void foo(signed char);
 |    void foo(unsigned char x) { }
 | but in C++ it's legal.  It would be nice to have a switch that
 | gave a warning when you make a mistake like that.
 Well, I'm not sure we wanted a -Wpossibly-misoverloading (which may
 include overloads that are not overrinding) than a
 -Wmissing-declarations.  It is /typical/ in C++ to define a "global"
 (mor accurately a nemspace-scope) function with no preceding
 declaration.  The -Wmissing-declarations is much about detecting
 "auto-prototyping" function use than detecting mis-overloading.
 I would suggest we keep separate these two separate issues.
 -- Gaby

             reply	other threads:[~2002-10-15 11:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-15  4:36 Gabriel Dos Reis [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-15  5:42 bangerth
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).