Closed p5pRT closed 12 years ago
In handy.h\, we use #ifndef UINT64_C to guard defining both UINT64_C and INT64_C. This means that clever users\, namely those defining their own macros and not using \<inttypes.h> in their XS code\, can end up with a redefinition of INT64_C. One example we tripped over recently was using boost\, in boost/date_time/compiler_config.hpp ... which defines only INT64_C and not UINT64_C.
I believe this bug is still there in blead.
(And if anyone could figure out how to electrocute anyone trying to write C++ XS using Boost\, please send me the recipe!)
still present in blead's handy.h
@iabyn - Status changed from 'new' to 'open'
This should be fixed by 80524f3\, but I don't have anything to test this with. If it still causes problems\, feel free to reopen the ticket.
-doy
This should be fixed by 80524f3\, but I don't have anything to test this with. If it still causes problems\, feel free to reopen the ticket.
-doy
@doy - Status changed from 'open' to 'resolved'
Migrated from rt.perl.org#76306 (status was 'resolved')
Searchable as RT76306$