From owner-freebsd-current@FreeBSD.ORG  Tue Nov 12 21:28:35 2013
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id E18E64A6
 for <freebsd-current@freebsd.org>; Tue, 12 Nov 2013 21:28:35 +0000 (UTC)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.22])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA (128/128 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 719272838
 for <freebsd-current@freebsd.org>; Tue, 12 Nov 2013 21:28:35 +0000 (UTC)
Received: from mandree.no-ip.org ([78.48.103.134]) by mail.gmx.com (mrgmx101)
 with ESMTPSA (Nemesis) id 0MGWR2-1VtYw52HSq-00DFuK for
 <freebsd-current@freebsd.org>; Tue, 12 Nov 2013 22:28:33 +0100
Received: from [IPv6:::1] (localhost6.localdomain6 [IPv6:::1])
 by apollo.emma.line.org (Postfix) with ESMTP id 62F8223CE8F
 for <freebsd-current@freebsd.org>; Tue, 12 Nov 2013 22:28:32 +0100 (CET)
Message-ID: <52829D80.6000303@gmx.de>
Date: Tue, 12 Nov 2013 22:28:32 +0100
From: Matthias Andree <matthias.andree@gmx.de>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: freebsd-current@freebsd.org
Subject: Re: Are clang++ and libc++ compatible?
References: <20131112163219.GA2834@troutmask.apl.washington.edu>	<77CB2B92-216A-4C80-B033-7E582B5F0DFC@FreeBSD.org>	<20131112165422.GA2939@troutmask.apl.washington.edu>
 <CAGsORuAEP-dag2AqO=n66QG9GZf9z3DKqM+fYBK5Txzeqbwhuw@mail.gmail.com>
In-Reply-To: <CAGsORuAEP-dag2AqO=n66QG9GZf9z3DKqM+fYBK5Txzeqbwhuw@mail.gmail.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:dBUKFBNZDTv6PqZN6VuUXkzQOsca6mD9p6wjXle4SE/uFveQnhx
 PHZpx/+4U6EEde7sujhUKdJSTxtQvAWgGcHFhUPPwhEIFWi+zwBumgGgXrexOFtQDtg/RnU
 zNmeUMtk9/IzmP0CbH7A6I00WKecM9HOKZKGXszN679svLRQS2JBJPY1D5XFQcgz5e9ik6s
 /qQLZ9JMEqIemxNNrfKOA==
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.16
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Nov 2013 21:28:35 -0000

Am 12.11.2013 18:13, schrieb Zhihao Yuan:

> BTW, iirc VC STL has the same issue.  But libstdc++ has an honorable
> history of supporting incomplete type in STL declaration.

A disservice, not honorable.

Nonstandard extensions, however convenient, are a pain when writing
portable code.  I am usually setting -std=c++11 -pedantic first up these
days to avoid pitfalls later. (or -std=c11)  And hope the compiler
actually complains.