Re: [boost] warning suppression

From: Andreas Huber (ahd6974-spamboostorgtrap_at_[hidden])
Date: 2007-08-12 18:09:25

Hi Yuval

"Yuval Ronen" <ronen_yuval_at_[hidden]> wrote in message 
news:f9nak5$i45$1_at_sea.gmane.org...
>> simple_state<> ultimately derives from noncopyable, which is why the 
>> warnings
>> are generated in the first place. Popping at the end of the header would
>> suppress the warnings for simple_state<> but would produce warnings for
>> MyState. Since I believe that *all* users who care about warnings will 
>> disable
>> these in their code anyway, I think the most user-friendly approach is to
>> permanently disable them in the library header.
>
> I'm not sure these warnings are caused by derivation from noncopyable. I
> tried to compile
>
> class A : private boost::noncopyable { };
>
> in warning level 4 and got no warnings at all. I only get those
> 4511/4512 warnings when I write a class with a data member (not base
> class) that is not CopyConstrucible/Assignable.

Ok, that could indeed be the case for my code as well. I'll look into it.

Thanks for the hint!

Regards,

-- 
Andreas Huber
When replying by private email, please remove the words spam and trap
from the address shown in the header.