BOOST_STRONG_TYPEDEF conflicting defs in 1.47

There seem to be conflicting definitions for the BOOST_STRONG_TYPEDEF macro: 11>e:\dev\devel\libs\boost\boost_1_47_0\boost\strong_typedef.hpp(45) : warning C4005: 'BOOST_STRONG_TYPEDEF' : macro redefinition 11> e:\dev\devel\libs\boost\boost_1_47_0\boost\serialization\strong_typedef.hpp(45) : see previous definition of 'BOOST_STRONG_TYPEDEF' They are slight different, but function identically (i.e., the one in serialization has an explicit default constructor call on the member variable t). Are both of these necessary, or should serialization just use the default one from the boost directory? Thanks, Michael Goldshteyn

Michael Goldshteyn wrote:
There seem to be conflicting definitions for the BOOST_STRONG_TYPEDEF macro:
11>e:\dev\devel\libs\boost\boost_1_47_0\boost\strong_typedef.hpp(45) : warning C4005: 'BOOST_STRONG_TYPEDEF' : macro redefinition 11> e:\dev\devel\libs\boost\boost_1_47_0\boost\serialization\strong_typedef.hpp(45) : see previous definition of 'BOOST_STRONG_TYPEDEF'
They are slight different, but function identically (i.e., the one in serialization has an explicit default constructor call on the member variable t). Are both of these necessary, or should serialization just use the default one from the boost directory?
Hi, it seems that boost\strong_typedef.hpp has been deprecated and includes on trunk boost\serialization\strong_typedef.hpp. Best, Vicente -- View this message in context: http://boost.2283326.n4.nabble.com/BOOST-STRONG-TYPEDEF-conflicting-defs-in-... Sent from the Boost - Dev mailing list archive at Nabble.com.

"Vicente Botet" wrote in message news:1314718628914-3779052.post@n4.nabble.com...
They are slight different, but function identically (i.e., the one in serialization has an explicit default constructor call on the member variable t). Are both of these necessary, or should serialization just use the default one from the boost directory?
Hi, it seems that boost\strong_typedef.hpp has been deprecated and includes on trunk boost\serialization\strong_typedef.hpp.
That's good to know... Thanks, Michael Goldshteyn
participants (2)
-
Michael Goldshteyn
-
Vicente Botet