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.php.net/u
Hi Jessie,
Regarding the name resolution rules, I posted a patch a few months
ago with what I think is a more reasonable lookup order (http://news.php.net/php.internals/34097
), but did not get much feedback. Would you like to try it out? (let
me know if it doesn't apply cleanly against the
Hi,
This is a clear bug, please report it at bugs.php.net
Done: http://bugs.php.net/44653
Since "use SomeName" does the same as "use ::SomeName" dropping the
warning also be an option.
And if we split of "use" into "use namespace" and "use class" we could
resolve ambiguous calls where
a
Julian Reich wrote:
Hi,
I recently started porting an application to PHP 5.3.
1. While testing the new namespace implementation I noticed the following:
Executing the code above results in a warning: "The use statement with
non-compound name 'Test1' has no effect in [...]".
I understand the r
Julian,
Regarding the name resolution rules, I posted a patch a few months ago
with what I think is a more reasonable lookup order
(http://news.php.net/php.internals/34097), but did not get much
feedback. Would you like to try it out? (let me know if it doesn't apply
cleanly against the curre
