From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6358 invoked by alias); 6 Jan 2004 23:00:23 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 6351 invoked by uid 48); 6 Jan 2004 23:00:22 -0000 Date: Tue, 06 Jan 2004 23:00:00 -0000 Message-ID: <20040106230022.6350.qmail@sources.redhat.com> From: "bangerth at dealii dot org" To: gcc-bugs@gcc.gnu.org In-Reply-To: <20040106205426.13590.boris@kolpackov.net> References: <20040106205426.13590.boris@kolpackov.net> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug c++/13590] unexpected overload resolution X-Bugzilla-Reason: CC X-SW-Source: 2004-01/txt/msg00573.txt.bz2 List-Id: ------- Additional Comments From bangerth at dealii dot org 2004-01-06 23:00 ------- That's not a good example. The using directive for A::f and B::f create an ambiguity, but this only needs to be detected when you try to call one of the functions, i.e. during overload resolution, not when the using directive is parsed. However, you call f(int), and there is no ambiguity in this case. W. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13590