Hi Sebastian,
This is not really a good example as the getInstance() method alone is
> not sufficient for a reusable implementation of the Singleton pattern.
>
Yes, it was just a pseudo-code and not a true singleton implementation.
> A trait for a reusable implementation of the Singleton pa
> I groupped the the 5.3.4RC1 entries: http://dpaste.com/277482/plain/
>
> Is it okay to commit? :)
>
>
Wouldn't it be better to group PHP-FPM changes in a single block rather than
two separate for additions and fixes?
/Simas
Hi Ferenc,
for reusable singleton pattern with php 5.3
> http://www.slideshare.net/fabpot/design-patternrevisitedphp53
> slide 11 and 12
>
As Tom already pointed out - there is that lock-down of your parent(s) to
singletons with this type of implementation and there are other shortcomings
when u
Hi Stefan,
Following the motto 'it is just compiler assisted copy and paste' I think
> it should be implemented.
>
Alright then, I am sure someone will find more uses for static methods in
Traits like factories/utilities (especially if traits can be made to work
with late static binding).
I ass
Hello,
I was just skimming through Traits RFC document on the wiki trying to find a
practical use for them. The first thing that comes to my mind is a Singleton
implementation - this is where I found myself literally "copying" most of
the code in the past. As far as I know there is no way to imple
