Mailing-List: contact dev-help@stdcxx.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@stdcxx.apache.org
Received-SPF: pass (athena.apache.org: domain of msebor@gmail.com designates
 74.125.46.30 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:organization:user-agent:mime-version:to
         :subject:content-type:content-transfer-encoding:sender;
        b=ZqrdMLcv57MGM8mlA6GOFDBjOtBuOdzuZtCfM7x1Wi8n6lDwuscSHiWf3Ia9yZZTQt
         AyZgpSBhI8ttTWOlKMJ5JBHMjbrPwQYp/kfxDpUduNopt/FEii9BnhoF/s4+ec/SNmAf
         3hQ0mIdNGU0hRBfBdrpe4W5reLQKrHmpERxY4=
Message-ID: <486955F9.3080205@roguewave.com>
Date: Mon, 30 Jun 2008 15:54:01 -0600
From: Martin Sebor <sebor@roguewave.com>
Organization: Rogue Wave Software, Inc.
User-Agent: Thunderbird 2.0.0.14 (X11/20080501)
MIME-Version: 1.0
To: dev@stdcxx.apache.org
Subject: C++ 0x testing
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: Martin Sebor <msebor@gmail.com>

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.

Martin