Hmm, wouldn't it be better to use here #pragma push_macro/pop_macro with undefine instead?
Btw, in what context you hit this issue that within C++ _Bool was defined already? Regards, Kai 2016-05-25 13:26 GMT+02:00 Hugo Beauzée-Luyssen <[email protected]>: > --- > mingw-w64-headers/crt/yvals.h | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/mingw-w64-headers/crt/yvals.h b/mingw-w64-headers/crt/yvals.h > index 70593c4..98b6921 100644 > --- a/mingw-w64-headers/crt/yvals.h > +++ b/mingw-w64-headers/crt/yvals.h > @@ -163,10 +163,12 @@ > #define _Restrict __restrict__ > > #ifdef __cplusplus > +#ifndef _Bool > _STD_BEGIN > typedef bool _Bool; > _STD_END > #endif > +#endif > > #define _LONGLONG /* __MINGW_EXTENSION */ __int64 > #define _ULONGLONG /* __MINGW_EXTENSION */ unsigned __int64 > -- > 2.8.1 > > > ------------------------------------------------------------------------------ > Mobile security can be enabling, not merely restricting. Employees who > bring their own devices (BYOD) to work are irked by the imposition of MDM > restrictions. Mobile Device Manager Plus allows you to control only the > apps on BYO-devices by containerizing them, leaving personal data untouched! > https://ad.doubleclick.net/ddm/clk/304595813;131938128;j > _______________________________________________ > Mingw-w64-public mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/mingw-w64-public ------------------------------------------------------------------------------ Mobile security can be enabling, not merely restricting. Employees who bring their own devices (BYOD) to work are irked by the imposition of MDM restrictions. Mobile Device Manager Plus allows you to control only the apps on BYO-devices by containerizing them, leaving personal data untouched! https://ad.doubleclick.net/ddm/clk/304595813;131938128;j _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
