Re: c++/8821: gcc 3.2 problem with overloaded inherited operator

[Wolfgang Bangerth <bangerth@ticam.utexas.edu>]

The following reply was made to PR c++/8821; it has been noted by GNATS.

From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: Nathan Sidwell <nathan@codesourcery.com>
Cc: andre@kiwisound.de, <gcc-bugs@gcc.gnu.org>, <gcc-gnats@gcc.gnu.org>
Subject: Re: c++/8821: gcc 3.2 problem with overloaded inherited operator
Date: Wed, 11 Dec 2002 09:19:58 -0600 (CST)

 > > how operators behave. That's the question here. I concede that the 
 > > behavior is confusing.
 > First name lookup happens, once a name has been found, base classes
 > are not searched.
 > Then overload resolution happens
 > then accessibility is checked
 > 
 > This happens consistently regardless of virtuality or operatorness
 
 I was confused, sorry. (I guess mainly be the existence of 
 -Woverloaded-virtual, which suggests that virtual functions behave 
 differently.) Volker already pointed out the right paragraph of the 
 standard, and y'all are right, of course.
 
 Thanks for so bravely trying to enlighten me ;-)
   Wolfgang
 
 -------------------------------------------------------------------------
 Wolfgang Bangerth              email:           bangerth@ticam.utexas.edu
                                www: http://www.ticam.utexas.edu/~bangerth