Should I go with the Singleton Pattern or wait for 5.3?

Hello, I'm planning out a simple project and most probably I will need
the functionality provided by the Singleton pattern.
However with the next 5.3 release I would be able to conveniently use
classes directly without instancing them.
This would be a comparable option thanks to late state binding and the
possibility to reference the class using a variable.

What path do you suggest I should take? I can wait for the 5.3 release
since I'm not in a hurry.
I would like to hear your opinions in particular regarding the
performance and code maintainability aspects.

Thanks for your time.

Luigi Perroti wrote:
> Hello, I'm planning out a simple project and most probably I will need
> the functionality provided by the Singleton pattern.
> However with the next 5.3 release I would be able to conveniently use
> classes directly without instancing them.
> This would be a comparable option thanks to late state binding and the
> possibility to reference the class using a variable.
>
> What path do you suggest I should take? I can wait for the 5.3 release
> since I'm not in a hurry.
> I would like to hear your opinions in particular regarding the
> performance and code maintainability aspects.

Is this a decision for the whole project or just one particular part of
it? Can that one part be put off until later or does it need to be done
first?

--
Postgresql & php tutorials
http://www.designmagick.com/

On Tue, Jul 15, 2008 at 2:10 AM, Chris wrote:
>
> Is this a decision for the whole project or just one particular part of
> it? Can that one part be put off until later or does it need to be done
> first?
>

This decision will impact the whole project.

I think that maybe I should go with the Singleton pattern approach
since it should allow for easier/quicker refactoring in case I have to
switch to another object oriented pattern.

BTW, thanks for your other reply on the php-db list.