Re: [PHP-DEV] early class binding revisited

2008-01-26 Thread phpxcache
any news on this topic? -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP-DEV] early class binding revisited

2007-12-30 Thread phpxcache
more pitfall: apc and XCache uses fast copy of opcodes for restoring opcode, but this will never work if early binding which have to modify opcodes is done after restore see apc_copy_op_array_for_execution() in apc_compile.c there is my_copy_data_exceptions(dst, src); which do a check if to deep co

Re: [PHP-DEV] early class binding revisited

2007-12-30 Thread phpxcache
> Compiler shouldn't generate different code. Unqualified name is resolved > at runtime, but code should be the same whatever resolution was made. > Did you check that different code is indeed generated? zend_compile.c === if (zend_hash_find(CG(class_table), lc

Re: [PHP-DEV] early class binding revisited

2007-12-30 Thread Stanislav Malyshev
5.3 namespace code will check for CG(class_table) and see if a class is internal class to generate different code. Compiler shouldn't generate different code. Unqualified name is resolved at runtime, but code should be the same whatever resolution was made. Did you check that different code i

[PHP-DEV] early class binding revisited

2007-12-30 Thread phpxcache
= original problem = the biggest problem caused by early class binding is that it's unfriendly to opcode cachers. parent1.php class P { function __construct() { echo "parent2"; } } include "child.php" == parent2.php class P { function __constr