Re: [boost] [warnings] Are warnings acceptable artifactsfrom builds?

Subject: Re: [boost] [warnings] Are warnings acceptable artifactsfrom builds?
From: Stewart, Robert (Robert.Stewart_at_[hidden])
Date: 2009-09-09 11:19:26

Steven Watanabe wrote:
> Stewart, Robert wrote:
> > Thomas Klimpel wrote:
> >
> >> #ifdef BOOST_WARNING_MSVC_WORKAROUND
> >> #pragma warning(push)
> >> #pragma warning(disable:4127)
> >> #endif
> >>
> >> ...
> >>
> >> #ifdef BOOST_WARNING_MSVC_WORKAROUND
> >> #pragma warning(pop)
> >> #endif
> >
> > Those could easily be macros, thus reducing the source code burden.
>
> I'd be interested to see how.  The best way of handling it that
> I'm familiar with is
>
> #include <boost/library/detail/disable_warnings.hpp>
>
> #include <boost/library/detail/enable_warnings.hpp>

Hmmm, my preprocessor skills are not great (a good thing!), so I probably spoke out of turn.  I should just leave things like that to someone like Paul Mensonides.

Still, a library could create a pair of headers and include them around the suppression regions, thus reducing the source code burden as I thought a macro could.  I believe a macro can be used to generate a filename for an include directive, so different warnings could be suppressed using a generalized pattern, right?

_____
Rob Stewart                           robert.stewart_at_[hidden]
Software Engineer, Core Software      using std::disclaimer;
Susquehanna International Group, LLP  http://www.sig.com

IMPORTANT: The information contained in this email and/or its attachments is confidential. If you are not the intended recipient, please notify the sender immediately by reply and immediately delete this message and all its attachments. Any review, use, reproduction, disclosure or dissemination of this message or any attachment by an unintended recipient is strictly prohibited. Neither this message nor any attachment is intended as or should be construed as an offer, solicitation or recommendation to buy or sell any security or other financial instrument. Neither the sender, his or her employer nor any of their respective affiliates makes any warranties as to the completeness or accuracy of any of the information contained herein or that this message or any of its attachments is free of viruses.