Beman d339470e6e Remove "explicit" from Endian type constructors. Rationale: Having to write "cntr.insert(big_int32_t(value))" instead of "cntr.insert(value)" gets old fast when you are writing application code and the use case arises more or less continuously. Additionally, the use of an endian type is an implementation detail that should not leak into the application code that needs to create values of the type. Furthermore, the ambiguities that caused the constructors to be made explicit no longer occur; they were eliminated when BOOST_MINIMAL_INTEGER_COVER_OPERATORS was introduced to removed a dependency on boost/operators.hpp. If an ambiguity does arise, it is easy to clear via a static_cast or a function-style cast.

2013-09-06 10:36:54 -04:00

..

conversion.html

Fix boo boos detected by inspect program.

2013-05-29 09:40:35 -04:00

do_list.html

Add do-list item fixing <boost/detail/endian.hpp> licensing issue.

2013-03-25 08:27:37 -04:00

done_list.html

Last pass through docs

2013-05-28 11:04:03 -04:00

index.html

Add breaking changes heads up

2013-09-01 09:10:00 -04:00

types.html

Remove "explicit" from Endian type constructors. Rationale: Having to write "cntr.insert(big_int32_t(value))" instead of "cntr.insert(value)" gets old fast when you are writing application code and the use case arises more or less continuously. Additionally, the use of an endian type is an implementation detail that should not leak into the application code that needs to create values of the type. Furthermore, the ambiguities that caused the constructors to be made explicit no longer occur; they were eliminated when BOOST_MINIMAL_INTEGER_COVER_OPERATORS was introduced to removed a dependency on boost/operators.hpp. If an ambiguity does arise, it is easy to clear via a static_cast or a function-style cast.

2013-09-06 10:36:54 -04:00

vc++readme.txt

Copy from README

2013-05-29 10:37:44 -04:00