On Sun, 17 Aug 2003 18:29:01 +0100, Nigel Rantor wrote:
> Mark Fowler wrote:
> > You shouldn't. Really. You should subclass the other method.
>
> Well, I agree, but I also wanted to get on to the multiple inheritence
> angle to see what you lot thought about it. So in a sense, I would like to
> force you to do what you don't want to. :-)
> >>If you don't pollute their name space then do you have to release a
> >>class that has the extensions in it and make people instantiate that
> >>class?
> >
> > Yes, this is the normal thing to do.
>
> Yep, leading on to the MI problem...
What MI problem? As far as I remember, C++ people don't like diamond
inheritance, but it didn't sound like that was going to be a problem here,
even if you do end up with diamonds.
--
Peter Haworth [EMAIL PROTECTED]
"All those who believe in psychokinesis, raise my hand!"
