From: Bronek Kozicki (brok_at_[hidden])
Date: 2005-11-02 11:55:22
David Abrahams <dave_at_[hidden]> wrote:
>> I believe that this is best solution, that should be used in other
>> places in boost where we see these warnings. My opinion is based on
>> experience with very large project where each compiler warning is
>> treated as compilation error. We do have warnings (sometimes even in
>> std:: headers) , thus we disable specific warnings in specific places
>> where we believe particular warning is harmless. This allows our code
>> (several MLOC) to compile sucesfully.
> If we want to go that way, we're going to need standard prefix and
> postfix headers that we #include in every Boost header:
> #ifndef INCLUDE-GUARD
> # define INCLUDE-GUARD
> # include <boost/config/prefix.hpp>
> ...your code here
> # include <boost/config/postfix.hpp>
> #endif // INCLUDE-GUARD
> Otherwise it will be totally unmaintainable.
Hm, as this is actually workaround, why not apply it only locally? That
is, just around the location inside header file that needs such special
treatment? This is how we manage these problems in our codebase.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk