Question

I’m looking for a good, clean way to go around the fact that PHP5 still doesn’t support multiple inheritance. Here’s the class hierarchy:

Message
— TextMessage
——– InvitationTextMessage
— EmailMessage
——– InvitationEmailMessage

The two types of Invitation* classes have a lot in common; i’d love to have a common parent class, Invitation, that they both would inherit from. Unfortunately, they also have a lot in common with their current ancestors… TextMessage and EmailMessage. Classical desire for multiple inheritance here.

What’s the most light-weight approach to solve the issue?

Thanks!

Answer 1

Alex, most of the times you need multiple inheritance is a signal your object structure is somewhat incorrect. In situation you outlined I see you have class responsibility simply too broad. If Message is part of application business model, it should not take care about rendering output. Instead, you could split responsibility and use MessageDispatcher that sends the Message passed using text or html backend. I don’t know your code, but let me simulate it this way:

$m = new Message(); $m->type = 'text/html'; $m->from = 'John Doe <[e-mail]>'; $m->to = 'Random Hacker <[e-mail]>'; $m->subject = 'Invitation email'; $m->importBody('invitation.html');  $d = new MessageDispatcher(); $d->dispatch($m); 

This way you can add some specialisation to Message class:

$htmlIM = new InvitationHTMLMessage(); // html type, subject and body configuration in constructor $textIM = new InvitationTextMessage(); // text type, subject and body configuration in constructor  $d = new MessageDispatcher(); $d->dispatch($htmlIM); $d->dispatch($textIM); 

Note that MessageDispatcher would make a decision whether to send as HTML or plain text depending on type property in Message object passed.

// in MessageDispatcher class public function dispatch(Message $m) {     if ($m->type == 'text/plain') {         $this->sendAsText($m);     } elseif ($m->type == 'text/html') {         $this->sendAsHTML($m);     } else {         throw new Exception("MIME type {$m->type} not supported");     } } 

To sum it up, responsibility is split between two classes. Message configuration is done in InvitationHTMLMessage/InvitationTextMessage class, and sending algorithm is delegated to dispatcher. This is called Strategy Pattern, you can read more on it here.