On 04/22/2013 12:55 AM, Robert Stoll wrote: > I agree with Igor. The readability could be improved and I do not see the > problem of hiding built-in php functions (however, I would not recommend > it). > I would say, if someone hides the normal php built-in function then he or > she is doing that on purpose and is aware of the consequences. Thus it is > also fine if the same person imports the function, which hides the normal > php built-in function, in another namespace.
Huge +1 from me. I know that using only functions instead of OOP in PHP has this 90s-PHP3-Vibe to it, but as a matter of fact you can write mostly side-effect free code using only functions in PHP. This would make using functions much more flexible and even more importantly, consistent to everything else. The only downside to this proposal, as Stas correctly mentioned is that it would allow people to shoot themselves in the foot when using weird import behavior. But as you deliberately have to misuse this I don't see any real harm. Something like instance variable shadowing in Java is much, much more error-prone and still hardly anyone complains about this kind of feature. Greetings, Florian -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
