This does seem strange. To me the error message looks fine, but it is weird
that "MethodOne" works while "MethodTwo" doesn't. Seems like both should
fail in a perfect world. However, this seems like a situation where bad
code is tickling some weird corner case in PHP, not a situation where PHP i
Hello,
On Tue, Oct 4, 2011 at 11:28 PM, Christian Kaps
wrote:
>
>
> It's available since PHP 5.3. This feature is called "late static binding".
>
Before anyone else responds to my post, please read the entire message!
It's simple really, the error message is odd and misleading for the
example c
>>
>>
>>
>>
> In addition, as I understand and would like to make you aware that
> static is not allowed in compile time class constants. Which is
> slightly unusual and perhaps could be changed because it seems that
> there is already runtime resolving taking place here.
>
It's available si
Hello,
On Tue, Oct 4, 2011 at 11:33 AM, Matthew Weier O'Phinney
wrote:
>
> That makes complete sense to me -- ClassA is referring to self, which
> resolves to ClassA... which does not define a "VERSION" constant. Change
> to this:
>
> public $version = static::VERSION;
>
> and it should be fin
On 2011-10-03, Chris Stockton wrote:
> Hello,
>
> I noticed the following odd behavior earlier today, there is
> definitely a bug here in my opinion, the bug is either the error
> message or the behavior. I think the behavior is possibly expected.
> I'll let some others comment.
>
> The reason I t
