[boost] FW: Boost Unit Test Framework: Localisation hiccups

From: Rozental, Gennadiy (gennadiy.rozental_at_[hidden])
Date: 2002-11-25 04:54:59

> Dear Gennadiy,
>     I've just been trying out the latest (1.29.0) release of the Boost >
Unit Test Framework.  I ran into a few minor localisation hiccups you
> might want to be told about.

> I'm using Metrowerks Codewarrior 8.1 on MacOS 9.2.  A couple of 
> problems resulted directly from this.

> 1) At line 45 of execution_monitor.cpp the test
> #if defined(_MSC_VER) || (defined(__MWERKS__) && __MWERKS__ >= 0x3000)

> yielded a false positive.  I altered it to
> #if defined(_MSC_VER) || (defined(__MWERKS__) && defined(__INTEL__) &&
> __MWERKS__ >= 0x3000)

Could Metrowerks users conferm that this is the best way to separate Mac and
everything else?

> 2) In cstdint.hpp importing the C99 typedefs failed.  When compiled as >
C++,
> the MW version of <stdint.h> behaves by analogy with the other standard
> headers: it defines the typedefs in std:: and then exports them to the
> global namespace with using declarations.  Unfortunately, this seems to
> mean that when cstdint.hpp tries to import them from the global
> namespace, they aren't really there.  I've hacked a copy of
> cstdint.hpp to work by just sticking std:: in where needed, but
> something more robust needs to be done here.

Could this author reply to this?

Gennadiy.