15 Nov
2009
15 Nov
'09
12:10 p.m.
On Sun, Nov 15, 2009 at 9:32 AM, Andrey Semashev <andrey.semashev@gmail.com>wrote:
joel wrote:
Emil Dotchevski wrote:
I suspect however that we would have had the same issue even if object_hex_dump.hpp did #include <stdlib.h>. Isn't it too risky for mpl to define its own size_t?
Maybe it's a naive question but, isn't it <cstddef> that should be included to get size_t in std ?
Or even better: boost/compatibility/cpp_c_headers/cstddef.
Is there anywhere where all this wisdom is written down - a kind of "Boost Common Knowledge" page(s)? - Rob.