Re: [Quantlib-dev] disabling compilation warnings

[Luigi B. <lui...@gm...>]

On Fri, 2007-05-25 at 17:43 +0200, DU VIGNAUD DE VILLEFORT FRANCOIS
GASAPRD PHI wrote:
> Ok thks, what about the #4180 ?

It could be dealt with in the same way. What is the warning about?

Later,
	Luigi

P.S. About your suggestion of a macro such as:

#define QL_SAFE_BOOST_FUNCTION_INCLUDE \
#pragma warning (disable: 4224) \
etc.

I am not sure how the preprocessor works. If a pragma is inside a macro
definition, does it get executed when the preprocessor reads it (i.e.,
when the macro is defined, which doesn't make us any good) or when the
macro is expanded?


> -----Original Message-----
> From: Luigi Ballabio [mailto:lui...@gm...] 
> Sent: Friday, May 25, 2007 3:47 PM
> To: DU VIGNAUD DE VILLEFORT FRANCOIS GASAPRD PHI
> Cc: qua...@li...
> Subject: Re: [Quantlib-dev] disabling compilation warnings
> 
> On Fri, 2007-05-25 at 12:56 +0200, DU VIGNAUD DE VILLEFORT FRANCOIS
> GASAPRD PHI wrote:
> > I have just disabled the compilation warning #4224 for VC2005 by
> > adding the corresponding preprocessor command in ql/config.msvc.hpp.
> > I'm wondering if disabling uncommon compilation warning at a more
> > local level would'nt be more appropriated.
> 
> True--in fact, I did it locally in the 0.8.0 branch. It will appear in
> the trunk when we merge it.
> 
> Later,
> 	Luigi
> 
> 
> ---------------------------------------- 
> 
> Dealing with failure is easy: work hard to improve. Success is also 
> easy to handle: you've solved the wrong problem. Work hard to improve. 
> -- Alan Perlis 
> 
> 

---------------------------------------- 

Testing can never demonstrate the absence of errors in software, only 
their presence. 
-- W.E. Dijkstra