[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: KSelectAction
From:       Emily Ezust <yoamwmvs () umail ! corel ! com>
Date:       2000-02-24 17:17:48
[Download RAW message or body]

Stephan Kulow wrote:
> Emily Ezust wrote:
> > If you could do a b_object.set(3), then what should get plunked into
> > y? Since B objects have additional data warranting my overriding one
> > set function, it is likely that all my set functions need to be
> > overridden.
> >
> But isn't this with every function you can call in A? 

No, just the ones you override in B with different signatures. If you 
don't write any B::set functions you can still use A::set(int) 
in B through normal inheritance.
 
> Stroustroup arguments that using the same name for different things is
> most likely an error and the language helps you in detecting them in
> hiding
> the base class members with the same name (actually he does so in the
> context
> of multiple inheritance).

This doesn't contradicts what I'm saying. I'm assuming (with
the compiler) that the same name is usually used for similar things.

-- 
Emily Ezust, emilye@corel.com
Corel Corporation
(613)728-0826, x 5936
-- 
The address in the headers is not the poster's real email address.  Do not send
private mail to the poster using your mailer's "reply" feature.  CC's of mail 
to mailing lists are OK.  Problem reports to "postmaster@umail.corel.com".  
The poster's email address is "emilye@corel.com".

[prev in list] [next in list] [prev in thread] [next in thread]