It looks like that warning is generated due to /W64 (Detect 64-bit
portability issues) command line option. If you disable it I bet the
warning will go away. Although this option looks helpful, I think it
generates false possitives. For example it will generate a warning if you
assign a size_t to an unsigned int due to how size_t is defined with this
command line option enabled.
On Thu, 26 Jan 2006 03:37:33 -0700, gast128
Dear all,
Our company makes heavy use of boost libraries. But unfornately some libraries trigger warnings. This is hard to circumvent since we both have level 4 and warnings as error option enabled in Visual Studio 2003.
An example is the counting iterator:
const std::vector<int> values1(boost::make_counting_iterator(1), boost::make_counting_iterator(10));
gives C4244. This is even harder to supress since the STL is included in the precompiled header.
Is it an option to have a good look at this issue for the next release? Note that it is also possible that Plauger's STL is not conforming.
Wkr, me
-- Orhun Birsoy