From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2258 invoked by alias); 3 Apr 2007 23:30:40 -0000 Received: (qmail 2233 invoked by uid 48); 3 Apr 2007 23:30:32 -0000 Date: Tue, 03 Apr 2007 23:30:00 -0000 Message-ID: <20070403233032.2232.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug c++/29365] Unnecessary anonymous namespace warnings In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "crowl at google dot com" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2007-04/txt/msg00265.txt.bz2 ------- Comment #11 from crowl at google dot com 2007-04-04 00:30 ------- (In reply to comment #5) > Yes, sorry, I should have said if foo::bar is used in multiple TUs, rather than > foo itself. If foo::bar is defined in only one TU, and is used as an opaque > type in other TUs, you're fine. > > Perhaps we should suppress this warning in the main input file. The only remaining insecurity is when the same source is compiled twice in the same program or when a source is also include. These cases are probably rare enough to not warrant an option. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29365