15 Nov
2009
15 Nov
'09
10:10 p.m.
Andrey Semashev 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. Why is that better? It includes stddef.h and adds a couple of usings. Why is that better than cstddef (which does something a bit similar but moreish on gcc)? I don't understand, and would like to.
Patrick