Stefan Walk wrote: > On Friday 17 October 2008 04:02:32 Gregory Beaver wrote: >> Hi Stas, >> >> This is not what is proposed. The E_WARNING is *only* on a name >> conflict. Please re-read or try the patch: >> >> http://pear.php.net/~greg/resolve_conflict.patch.txt >> >> Greg > > Any particular reason why it defaults to seeing it as a namespace member > function and not as a static method call? I'd guess it "guesses wrong" more > often this way.
It avoids autoload attempts for namespace functions. Greg -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
