Date: 1999-12-19 15:43:57
Paul Moore writes:
> > The thing to do is define another macro, something like MSVCPP,
> > which you define only when it is really VC++, and then use this
> > macro to protect the workarounds.
> But then the *user* would need to define it in his builds. No - the compiler
> defines a macro which identifies itself. Other compilers shouldn't define it as
I meant to suggest that you put the MSVCPP macro in your library's
config header, with something like this:
#if defined(_MSC_VER) && !defined(__MWERKS__) ...
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk