On Thursday 27 December 2007, Hans Moog wrote: > In my oppinion namespaces should only be an additional way of > structering php elements and using short names again without loosing the > abilitiy to avoid naming conflicts with 3rd party libraries. Since > libraries are generally class libraries and because of already being > able to group variables, constants and functions in static classes i see > no reason for namespaces to affect the resolution of the previously > mentioned elements. Instead, they should only affect classes enabling > the coder to tie packages and use or provide libraries.
"Libraries are generally class libraries" is both wrong and very limiting. There is nothing wrong with functions. Thousands of professional web sites run on systems that have not a single class in them quite successfully. There are plenty of situations where going all OO is not a good thing, and results in more code complexity, not less. A "complete" namespace implementation supports both classes and functions equally. -- Larry Garfield AIM: LOLG42 [EMAIL PROTECTED] ICQ: 6817012 "If nature has made any one thing less susceptible than all others of exclusive property, it is the action of the thinking power called an idea, which an individual may exclusively possess as long as he keeps it to himself; but the moment it is divulged, it forces itself into the possession of every one, and the receiver cannot dispossess himself of it." -- Thomas Jefferson -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
