The patch didn't apply cleanly against current PHP_5_3. Therefore I
attached an adapted version.
Sorry, attachment missing: http://www.jreich.com/php/name_resolution.patch
Regards,
Julian Reich
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.ph
e I
attached an adapted version.
Regards,
Julian Reich
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
amespaced function and can save lookups at runtime.
Furthermore if traits were added to PHP we can simply use "use trait
TraitName". So there is no room
for confusion because of keyword reuse.
I think splitting of "use" was proposed on this list before but was
never discussed.
Reg
I think the current resolution order is a WTF-factor especially for
unexperienced users or users coming from other languages.
I know that the above arguments might have been already on this list
but I couldn't find some definitive decision to keep the current name
resolution order
Hi all,
Hi Timm,
How about:
return call_user_func_array(
array(new ReflectionClass($className), 'newInstance'),
$functionParameters
);
I also considered this possibility, but it looked like big overhead.
Am I wrong?
Yours sincerly,
Julian Reich
--
PHP Internals - PHP Runtime D
y to get new object
?>
I have written an implementation of new_object_array(); <-- see attachment
Perhaps some things need to be rewritten ;)
I would be happy if you would consider to include this function in the
standard distribution of php.
Yours sincerly,
Julian Reich
#include "p
ction be implemented and will it do what I assume?
Yours sincerly,
Julian Reich
([EMAIL PROTECTED])
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
