Hi!
And I'd ask - who wants to do new DB::mysql when they can just do mysql?
I do. Because this way I don't have to worry my mysql would clash with
someone other's mysql, and I can have all DB related stuff under one roof.
It can't clash if you don't "use" someone other's mysql namespace, or you
import it under a different alias. It's a very simple concept, honestly.
The common usage of use is going to be to get the name as short as
possible, and NOT have to type out db:: everywhere. Do you have code
There never was a task to make use of as little characters as possible. If
you think that was the point, you are mistaken. There were a task to make
it manageable, but not at the cost of clarity and robustness and
performance.
Are you the same guy who so furiously denied having to write "::" explicitly
for global functions/classes, for clarity, robustness and performance?
How did you switch that fast to the other end of the spectrum?
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
