This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Warnings for unhandled c++ exceptions?
- From: Alexandre Oliva <aoliva at redhat dot com>
- To: "Wesley W. Terpstra" <terpstra at ito dot tu-darmstadt dot de>
- Cc: gcc at gcc dot gnu dot org, Bonzini <bonzini at gnu dot org>
- Date: 03 Feb 2003 16:11:07 -0200
- Subject: Re: Warnings for unhandled c++ exceptions?
- Organization: GCC Team, Red Hat
- References: <002601c2cb78$2a3efbc0$29dd1d97@bonz><20030203164526.GA26049@ito.tu-darmstadt.de>
On Feb 3, 2003, "Wesley W. Terpstra" <terpstra@ito.tu-darmstadt.de> wrote:
> I suggested an optional flag to be used for compiler-assisted bug-tracking
> and quality code writing. (refer to the earlier portion of the message)
/me thinks such a warning would be mostly useless
I actually find this sad, but if you consider that most of the C++
code out there, as well as the C library whose declarations are
brought into C++, have no throw() declarations at all, you'd quickly
drown into warning due to calling methods that could throw anything
but that in reality don't, and it would be very difficult to tell what
warnings are actually significant.
> I presume someone else has already requested this functionality?
Yup. Searching the mailing list will, with some luck for picking the
right search terms, find a number of similar requests.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{redhat.com, gcc.gnu.org}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist Professional serial bug killer