From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7828 invoked by alias); 12 Apr 2012 15:20:35 -0000 Received: (qmail 7785 invoked by uid 22791); 12 Apr 2012 15:20:31 -0000 X-SWARE-Spam-Status: No, hits=-3.5 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from localhost (HELO gcc.gnu.org) (127.0.0.1) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 12 Apr 2012 15:18:48 +0000 From: "akim.demaille at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/52949] New: decltype too sensitive to order of declarations? Date: Thu, 12 Apr 2012 15:20:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: akim.demaille at gmail dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Message-ID: X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 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: 2012-04/txt/msg00878.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52949 Bug #: 52949 Summary: decltype too sensitive to order of declarations? Classification: Unclassified Product: gcc Version: 4.7.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned@gcc.gnu.org ReportedBy: akim.demaille@gmail.com Created attachment 27141 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=27141 Test case I am not sure of myself on this one. I have read a preversion of the standard (and I checked n2343 too), and I did not find anything very clear about this. I do understand that the "rich" version might require some dependency resolution in full generality, but then again, I have not found the restriction spelled out in the standard. The only restriction I spotted is the case of overloaded functions. I apologize if this is the expected behavior. In the following example, the first use of decltype fails because it does not see the member_ definition, which is right after it. The second decltype passes. $ g++-mp-4.7 --version g++-mp-4.7 (GCC) 4.7.0 Copyright (C) 2012 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. $ g++-mp-4.7 -std=c++11 foo.cc foo.cc:3:27: error: 'member_' was not declared in this scope foo.cc:3:27: error: 'member_' was not declared in this scope foo.cc: In function 'int main()': foo.cc:12:5: error: 'struct Vector' has no member named 'val1' $ g++-mp-4.8 --version g++-mp-4.8 (GCC) 4.8.0 20120408 (experimental) Copyright (C) 2012 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. $ g++-mp-4.8 -std=c++11 foo.cc foo.cc:3:27: error: 'member_' was not declared in this scope foo.cc:3:27: error: 'member_' was not declared in this scope foo.cc: In function 'int main()': foo.cc:12:5: error: 'struct Vector' has no member named 'val1'