Thread: Brainstorming: How to design this issue?

Hi,

I have a class Base and many Derived classes. All the Derived are identical (the same data members and functions) just the name differs Derived1, Derived2, etc.

Now the problem is that I receive a pointer to Derived1 and I should replay by sending a pointer to Derived3. Although all the Derived are the same I shoul still delete Derived1* and call new for Derived2 and deep copy all the contents from Derived1*.

Any ideas how to avoid new and deep copy and still have different names for Derived classes.

I hope I made myself understood.

BR,
Cristian

Hi,

Thanks Prelude and skipper.
I agree with you and I made the same proposition to my colleagues before: to have one class with a extra member "name": the reason the design was that they want to have the name of the class in the error logs... ;0).

BR,
Cristian.

PS: It was the same question...

OK, I may be saying a stupid thing as I didn't worked with multiple inheritance but here it is:
Base
/ | \
Derived1 - Derived2 Derived3

This should be read as:
Derived1, Derived2, Derived2 are Base
Derived2 is Derived1

So now when I receive a message I could do the following:
processMessage(Base * message) {
if (message is Derived1)
{
I process my message and send it back as Base*;
}

When the message is received the receiver would be able to make the cast to Derived2 because Derived2 is also a Derived 1. Am I right?, I get enthusiastic now...

If you wonder how I now which class a message is the answer is: by a field in the Base class that will be filled at the construction time.

I'm wondering if I am right?. I'll try to check myself too.

BR,
Cristian


}