> -----Original Message-----
> From: Martin Sebor [mailto:[EMAIL PROTECTED] On Behalf Of Martin Sebor
> Sent: Monday, June 30, 2008 3:54 PM
> To: dev@stdcxx.apache.org
> Subject: C++ 0x testing
>
> Unless I'm missing something, C++ 0x testing is currently disabled
> in nightly builds. I.e., because tests for the newly added C++ 0x
> features are guarded by the _RWSTD_NO_CXX_0X macro and because
> _RWSTD_EXT_CXX_0X is not #defined, the tests are compiled into
> what essentially amounts an empty main().
>
> With type traits and tuple being nearly done, I think it's time
> to start exercising these and any other new components in nightly
> builds. One approach that might be easily implementable at least
> for gcc is the one suggested in a recent thread: for 4.3.x, add
> -std=gnu++0x to the set of compiler options for gcc 4.3 and
> beyond, and make _RWSTD_EXT_CXX_0X synonymous with gcc's
> __GXX_EXPERIMENTAL_CXX0X__.
>
> Is there a better approach? I'd like to get things set up
> sometime this week.
Rather than hard-code the flags, I suggest a command-line make
definition; e.g. make _RWSTD_EXT_CXX_0X=1 ...
I thought this is the way it was originally proposed. Anyways,
the gcc.config flag appends the appropriate compiler flags and
defines only if this make variable is defined; e.g.
ifeq ($(_RWSTD_EXT_CXX_0X),1)
CXXFLAGS += -std=gnu++0x -D_RWSTD_EXT_CXX_0X
endif
Brad.
