From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12819 invoked by alias); 3 Nov 2008 17:45:44 -0000 Received: (qmail 5270 invoked by uid 48); 3 Nov 2008 17:44:21 -0000 Date: Mon, 03 Nov 2008 17:45:00 -0000 Subject: [Bug c++/38005] New: inconsistent precedence of operators in namespaces X-Bugzilla-Reason: CC Message-ID: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "c dot hite at rtsgroup dot net" 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: 2008-11/txt/msg00228.txt.bz2 (see #1) G++ seems to use different rules than sun for determining which operator is called. G++ gives an operator in the current namespace priority over another with more specific parameters in the global scope. (see #2) G++ does something very strange. When the current namespace contains the same operator overloaded for completely different parameters, the precedence of other operators changes. In all cases Sun's compiler prints "child". -- Summary: inconsistent precedence of operators in namespaces Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: c dot hite at rtsgroup dot net GCC build triplet: c24d5e9bda8759e6c069ef5eafbb8fe0 GCC host triplet: gcc version 4.2.3 GCC target triplet: i686-pc-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38005