> Your patch does not fix the problem at all. Ah, I see I got the Intel version check backwards, fixed (hopefully!)
> In my opinion, it can even > break some working configurations. I would rather use this conditional > expression: > > # if !(defined(_GLOBAL_USING) && (_GLOBAL_USING+0 > 0 || _CPPLIB_VER == > 310)) && !defined(_STD) I'm not convinced that _GLOBAL_USING is used consistently between Dinkumware libraries (windows vs linux etc), so I'd rather not rely on _GLOBAL_USING at all - hence my attempt to check the Intel version number. > since the test _GLOBAL_USING+0 > 0 is false although we want it true with > Dinkumware 3.10 (_CPPLIB_VER == 310 and maybe other versions but I don't > know them). If there is a way to test the macro _GLOBAL_USING is defined > but doesn't have a value, it would be even better: it would work with all > the versions of the library that assume "#define _GLOBAL_USING" to be > equivalent to "#define _GLOBAL_USING 1". I don't think it's possible to check for that as far as I know :-( John. _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
