From: Marc Espie <espie@quatramaran.ens.fr>
To: jbuck@racerx.synopsys.com
Cc: gcc@gcc.gnu.org
Subject: Re: Latest snapshot won't build with --enable-libstdcxx-v3
Date: Thu, 21 Sep 2000 17:40:00 -0000 [thread overview]
Message-ID: <200009220039.CAA09726@quatramaran.ens.fr> (raw)
In-Reply-To: <200009201530.IAA14094@racerx.synopsys.com>
In article < 200009201530.IAA14094@racerx.synopsys.com > you write:
>Warnings produced by the inclusion of system library header files are not
>acceptable, because it means that no user of the library can use flags
>like -Wall without being distracted by warnings from the system library.
>(Old-time Cygnoids are sure to remember how I always used to beat them
>up for this - libg++ used to always generate piles of warnings, I'd send
>lots of little patches to fix them, and then the next release would
>put them all back again).
>Putting in -Werror forces the developers to produce warning-free code.
I'd concur.
Not only that, but some people routinely compile some critical code with
a large list of warnings, plus -Werror... (the OpenBSD kernel, for instance).
so yes, having warnings in header code is a complete no-no.
next prev parent reply other threads:[~2000-09-21 17:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-19 11:44 Benjamin Scherrey
2000-09-19 15:08 ` Theodore Papadopoulo
2000-09-19 23:11 ` Benjamin Kosnik
2000-09-20 1:39 ` Theodore Papadopoulo
2000-09-20 8:32 ` Joe Buck
2000-09-20 8:42 ` Theodore Papadopoulo
2000-09-20 9:48 ` Phil Edwards
2000-09-21 17:44 ` Marc Espie
2000-09-21 17:40 ` Marc Espie [this message]
[not found] ` <mailpost.969583213.13372@postal.sibyte.com>
2000-09-21 17:59 ` Chris G. Demetriou
2000-09-21 23:32 ` Magnus Fromreide
2000-09-22 4:51 ` Gabriel Dos Reis
2000-09-25 15:12 ` Joern Rennecke
2000-09-20 5:29 ` Benjamin Scherrey
2000-09-20 9:14 ` Benjamin Scherrey
2000-09-20 9:33 ` Steven King
2000-09-20 12:29 ` Benjamin Scherrey
2000-09-20 12:52 ` Benjamin Kosnik
2000-09-20 13:16 ` Benjamin Scherrey
2000-09-21 11:59 ` Benjamin Scherrey
2000-09-20 10:18 ` Benjamin Kosnik
2000-09-21 20:54 Brad Lucier
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=200009220039.CAA09726@quatramaran.ens.fr \
--to=espie@quatramaran.ens.fr \
--cc=gcc@gcc.gnu.org \
--cc=jbuck@racerx.synopsys.com \
/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).