Subject: Re: [boost] Are warnings acceptable artifacts from builds?
From: Emil Dotchevski (emildotchevski_at_[hidden])
Date: 2009-09-11 19:07:54
On Fri, Sep 11, 2009 at 4:04 PM, Steven Watanabe <watanabesj_at_[hidden]> wrote:
> Emil Dotchevski wrote:
>> On Fri, Sep 11, 2009 at 11:31 AM, Stewart, Robert
>> <Robert.Stewart_at_[hidden]> wrote:
>>> Emil Dotchevski wrote:
>>>> If the "we want no warnings dammit" crowd main argument is "at my
>>>> company we have zero-warnings policy, we can't do anything about it"
>>>> then arguing whether or not any particular warning should be addressed
>>>> is pointless (OTOH, I'd bet that no company has zero-warnings policy
>>>> because some warnings can't be dealt with any other way but by
>>>> disabling them.)
>>> Disabling a warning, provided the scope is controlled, is fine.
>> Yes, but with GCC you can't control the scope.
> It isn't quite as fine-grained as msvc's mechanism, but you can use
> #pragma GCC system_header
> It seems to handle templates okay in recent versions.
I was wondering if the GCC pragma works well. If it really does, why
not just add it in boost/config and be done with it. :)
Reverge Studios, Inc.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk