19 Aug
2010
19 Aug
'10
8:20 p.m.
AMDG Andrey Semashev wrote:
On 19.08.2010 19:00, Steven Watanabe wrote:
Ralf Globisch wrote:
The same thing happened to me. One can define _SCL_SECURE_NO_WARNINGS to stop the warnings from appearing but I would prefer it if the problem could be fixed at source of the warnings. I'm guessing this can't be fixed until version 1.45?
We decided long ago that these warnings can't be reliably fixed from within Boost.
I think I worked around it in revision 64931.
Your fix looks like a good thing regardless of the warnings, since it avoid extraneous instantiations of basic_string. In Christ, Steven Watanabe P.S. The usual policy is to wait for the trunk tests to cycle before merging to the release branch.