I like the idea that DPs are idea-centered solutions. If you understand the basic idea; you can create anything in any language. However, while the Singleton is an interesting exercise on how to create a private class, remember, Singletons are evil.

Enjoy the Netherlands–wonderful people there. I attended the University of Leiden years ago. Great experience.

Kindest regards,
Bill

Great post! I always like to see DP on different languages and how do they come up with some technical solutions.

I remember when I first started programming with AS3 and tried to implement a Singleton. “No private constructor?! What the hell?!” I got really disappointed on that time but there are always some solutions. And in the case of the Singleton, a LOT of solutions.

That’s one of collest things about DP: they are idea-centered solutions. You implement it the best way you can.

Cheers (from the Nederlands now!)

Bill_BsB

Dude, it’s never too late to add good ideas!

First of all, thanks for the work-around for typing to an interface. Let me see if I’ve got this right. You set up the typing using the format set_someVariable(IdataType $someVariable);. That, I definitely will have to try.

Second, one of the ironies of Strict typing is that it aids in loose coupling. The reason is that typing to the interface commits you only to the interface and doesn’t tie you up with the implementation. You have to think:

Strict typing = Loose coupling

If strict typing ever comes to PHP, welcome it. It will loosen you up!

Kindest regards,
Bill

Thanks for the tip on using _autoload. I’ll give it a try for my next PHP design pattern.

Kindest regards,
Bill

Don’t know whether it’s too late or not. I want to share how i do “Program to interface not implementation” in PHP

here’s my code

public static function set_payment(IPayment $payment) {
// use type hinting to make sure that the $payment object
// must implement 'IPayment' interface (This is one what we
// looking for "program to interface not implementation")
$this->payment = $payment
.. some codes
$this->payment->process();
}


In my opinion this “Program to interface not implementation” phase rising up because the downside(pitfall) of “Strict type” language itself.

With any dynamic type languages you always come up with that phase.
e.g.

$i_payment = new ConcretThatImplementIPayment;
// is equivalent this line in flash
var i_payment:IPayment = new ConcreteThatImplementIPayment;


PS. May be there’s only me that think like this :)

In php you can do an __autoload to handle the includes.