GCC Bugreport

Alexandre Oliva oliva@lsd.ic.unicamp.br
Thu Sep 30 19:57:00 GMT 1999

On Sep 14, 1999, "Eijck, Ronald van" <eijckron@iquip.nl> wrote:

> MS VisualC 6.0 compiles this correctly. If I change the function name
> for Value() to AValue() GCC handles it correctly aswell. 

Nope, gcc handles it correctly in both cases, and MS Visual C is wrong
in accepting this code.  According to the C++ Standard, function names
in a derived class hide (not overload) functions of the base class
with the same name.

Alexandre Oliva http://www.dcc.unicamp.br/~oliva IC-Unicamp, Bra[sz]il
oliva@{dcc.unicamp.br,guarana.{org,com}} aoliva@{acm.org,computer.org}
** I may forward mail about projects to mailing lists; please use them

More information about the Gcc-bugs mailing list