But users of the PEAR solution to staticProperties may or may not want
any other portion of PEAR as well.
But they have the possibility to choose. ;)
So it's only "better" if it suits the needs of the user.
You'd have to ask the PEAR users if it's "better" for them.
1. I sent it here because I
On Fri, October 6, 2006 10:59 am, Hodicska Gergely wrote:
>> This would be Really Nifty, if PHP allowed multiple inheritence so
>> you
>> could have a mixin class...
>>
>> Otherwise, however, you have to have a common base class across all
>> the various class systems in use in your multitude of we
On Fri, October 6, 2006 7:22 am, Hodicska Gergely wrote:
> I'm curious about your opinion.
> class base
> {
> function &staticProperty($name, $value = null)
> {
> static $properties = array();
This would be Really Nifty, if PHP allowed
Hi!
I had a little discussion on a forum topic about static class method and
properties. Somebody there pointed to the PEAR::getStaticProperty()
solution to emulate static properties in PHP4. I was not familiar with
it but its approach seems a little strange for me. It is not really more
than st
Hi!
I had a little discussion on a forum topic about static class method and
properties. Somebody there pointed to the PEAR::getStaticProperty()
solution to emulate static properties in PHP4. I was not familiar with
it but its approach seems a little strange for me. It is not really more
than st
5 matches
Mail list logo
