From mboxrd@z Thu Jan  1 00:00:00 1970
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
Message-id: <200009220039.CAA09726@quatramaran.ens.fr>
References: <200009200838.e8K8ctO28043@mururoa.inria.fr> <200009201530.IAA14094@racerx.synopsys.com>
X-SW-Source: 2000-09/msg00515.html

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.