Re: [PATCH] Late Static Binding

From: Date: Thu, 02 Mar 2006 19:51:42 +0000
Subject: Re: [PATCH] Late Static Binding
References: 1 2 3 4 5 6 7 8  Groups: php.internals 
Request: Send a blank email to [email protected] to get a copy of this message
Hello Jeff,

Thursday, March 2, 2006, 8:21:08 PM, you wrote:

> On Mar 2, 2006, at 11:33 AM, Mike Lively wrote:

> Hi Mike,

>> In regards to naming: 'static' wasn't my first choice either. In fact I
>> was originally using 'this::' due to me misreading the notes from the
>> PDM.

> Does 'this' work ok?  I like that one.  this:: and $this would both be 
> late binding one for the class the other for the instance.  It makes a 
> lot of sense to me.  I think it explains why self isn't late binding, 
> too.  very nice.

> this::method()
> this::$property
> this::constant
> get_this_class()

>> (I doubt very strongly that anyone 'relies' on  early
>> binding for static functions...I could be wrong though.)

> But they do for static properties.  Changing the meaning of 
> self::$property would probably break some stuff.

Please no change of behavior and please not for the sake of wording
make things slower by cahing to do more slow string comparisons at
runtime becuase that is what self requires. Instead i like reusing
already existing keywords whose meaning would be easy understandable.
That said and after declining 'static' we are left with the following:

class::functionName()

Which is pretty good to me.

Best regards,
 Marcus


Thread (59 messages)

« previous php.internals (#22094) next »