> Deprecate it for 4.9.x.
> Remove it later. We don't need to keep around
> this macro which has been obsolete for at least
> two releases.
Agreed. Definitely deprecated for 4.9.
The internal style is to now check __cplusplus and in the future
whatever feature testing macros are developed.
-be
On Wed, Jul 3, 2013 at 4:39 PM, Ed Smith-Rowland <3dw...@verizon.net> wrote:
> While thinking about C++ n3694 feature test macros I noticed we still define
> __GXX_EXPERIMENTAL_CXX0X__ macro in c-family/c-cppbuiltin.c.
> We got rid of all uses of it in libstdc++.
> I propose we
On Wed, 3 Jul 2013, Ed Smith-Rowland wrote:
While thinking about C++ n3694 feature test macros I noticed we still define
__GXX_EXPERIMENTAL_CXX0X__ macro in c-family/c-cppbuiltin.c.
We got rid of all uses of it in libstdc++.
I propose we get rid of it here too.
User's shouldn't be
While thinking about C++ n3694 feature test macros I noticed we still define
__GXX_EXPERIMENTAL_CXX0X__ macro in c-family/c-cppbuiltin.c.
We got rid of all uses of it in libstdc++.
I propose we get rid of it here too.
User's shouldn't be relying on it. No?
OTOH, it may have been a
On 21 October 2010 18:52, Neal Becker wrote:
> I need a preprocessor macro to detect c++0x support. For now, that is
> __GXX_EXPERIMENTAL_CXX0X__
>
> but what happens once -std=c++0x is the default? Will this macro still
> be defined?
>
> Don't we need a
>
> __G
I need a preprocessor macro to detect c++0x support. For now, that is
__GXX_EXPERIMENTAL_CXX0X__
but what happens once -std=c++0x is the default? Will this macro still
be defined?
Don't we need a
__GXX_CXX0X__ ?
