I was thinking of the build of the entire library, when it would look more professional if all these warnings were suppressed. If headers contain calls to the deprecated functions, the Boost developers will have to decide on a policy for the library release, and document it. My vote would be to leave it up to the end user to define _CRT_SECURE_NO_DEPRECATE, as their company policy may be to disallow use of such software, so they need to be aware of it. - Keith MacDonald "Jonathan Turkanis" <technews@kangaroologic.com> wrote in message news:da6gkn$324$1@sea.gmane.org...
Keith MacDonald wrote:
I dont think defining _CRT_SECURE_NO_DEPRECATE in a header is acceptable.
I also agree. This should be defined in the bjam config file for TOOLS=vc-8_0, as I said earlier.
This will only help end users who build their applications with bjam. Also, a user may want to enable the deprecation warnings, because some of them may be useful.
Is that David Abraham's area of responsibility?
I think it's the responsibility of whoever volunteers, but I'm not sure it's a good idea.
- Keith MacDonald
Jonathan