WTF PHP?

[joepie91]

See http://sprunge.us/CaQX?php.

I can't even begin to understand how this is even possible.

 

[darknessends]

Is it happening specifically to this function or all of them ?

 

[SrsX]

Yep, PHP is drunk.

 

[joepie91]

Is it happening specifically to this function or all of them ?

It appears to be a recurring issue. In other words, PHP has a very nasty (and inconsistent) implementation of member variables.

 

[tchen]

Member calls and variables are on two separate lookup tables. ( ) automatically invokes a lookup in the method list, which doesn't have your closure since that has been assigned as a value. If you want to invoke on a member variable, then you need to call __invoke on the closure member variable.


$obj->lambda->__invoke( );

 

[telephone]

^^^

Or:

- Use "call_user_func_array($this->method, $args)"

- Use __call() with your own logic (still implementing call_user_func_array())

 

[joepie91]

Member calls and variables are on two separate lookup tables. ( ) automatically invokes a lookup in the method list, which doesn't have your closure since that has been assigned as a value. If you want to invoke on a member variable, then you need to call __invoke on the closure member variable.


$obj->lambda->__invoke( );

Problem is that this shouldn't be of any concern to a developer using PHP, rather than developing on the interpreter itself.

 

[tchen]

Problem is that this shouldn't be of any concern to a developer using PHP, rather than developing on the interpreter itself.

Half my brain is dedicated to memory structures, virtual tables (C++), interpreter/compiler expansions (especially Scala, and PHP magic methods), and garbage collectors.  So I can tell you with certainty, ALL languages have these types of deep knowledge issues.