From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-help-return-52643-listarch-gcc-help=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 14527 invoked by alias); 28 Mar 2013 09:08:37 -0000
Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-help.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-help/>
List-Post: <mailto:gcc-help@gcc.gnu.org>
List-Help: <mailto:gcc-help-help@gcc.gnu.org>
Sender: gcc-help-owner@gcc.gnu.org
Received: (qmail 14466 invoked by uid 89); 28 Mar 2013 09:08:30 -0000
X-Spam-SWARE-Status: No, score=-5.2 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,KHOP_RCVD_TRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE autolearn=ham version=3.3.1
Received: from mail-la0-f42.google.com (HELO mail-la0-f42.google.com) (209.85.215.42)    by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Thu, 28 Mar 2013 09:08:27 +0000
Received: by mail-la0-f42.google.com with SMTP id fe20so17340507lab.1        for <gcc-help@gcc.gnu.org>; Thu, 28 Mar 2013 02:08:25 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.152.105.244 with SMTP id gp20mr11979212lab.34.1364461705167; Thu, 28 Mar 2013 02:08:25 -0700 (PDT)
Received: by 10.112.31.169 with HTTP; Thu, 28 Mar 2013 02:08:24 -0700 (PDT)
In-Reply-To: <CAF1jjLtGAV3v5Dv=vP0DRRvffOrg_rU2vRzDkEbX3KdntEhgmA@mail.gmail.com>
References: <CAF1jjLtGAV3v5Dv=vP0DRRvffOrg_rU2vRzDkEbX3KdntEhgmA@mail.gmail.com>
Date: Thu, 28 Mar 2013 09:08:00 -0000
Message-ID: <CAH6eHdQzX=-x9iZS7aCU29Yiw7cHcU9FNq9iYMH_Hok3bAe+fA@mail.gmail.com>
Subject: Re: libstdc++ concept checking
From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: NightStrike <nightstrike@gmail.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Content-Type: text/plain; charset=ISO-8859-1
X-SW-Source: 2013-03/txt/msg00338.txt.bz2

On 28 March 2013 02:36, NightStrike wrote:
> This page:
>
> http://gcc.gnu.org/onlinedocs/libstdc++/manual/concept_checking.html
>
> says "They are off by default for all versions of GCC. They can be
> enabled at configure time with --enable-concept-checks. You can enable
> them on a per-translation-unit basis with -D_GLIBCXX_CONCEPT_CHECKS."
>
> I'm assuming that --enable-concept-checks is an option to use while
> building libstdc++ to set the default for that library.

Correct.

>  But does the
> second sentence mean that I can enable concept checking for my own
> code by defining that macro, even if libstdc++ wasn't compiled with
> the option turned on?

Yes, that's right.