Marc, This is not the right reason for naming it namespace.
Example: Say I am writing a new language. I want to introduce something similar to functions. But since OO is popular and sounds nice.. why not call it method on an object? People are asking for objects.. I'll just give them objects. It's not about the popularity of a word, but the meaning of it. If it resembles more of a package, let's call it package (as it does currently, namespace should be nested.. but that's my opinion). Regards, Olivier On 8/15/07, Marc Gear <[EMAIL PROTECTED]> wrote: > FWIW I am for "namespaces" because: > > - the functionality mentioned most often as missing in PHP is > 'namespaces'. People want 'namespaces' (see > http://en.wikipedia.org/wiki/PHP#Criticism) > - What they really want is no more clashing > classes/functions/variables when they integrate third party apps > (which the patch provides) > - What they also want is no more clashing objects/functions when a new > PHP extension becomes installed by default (Date anyone?) (which the > patch provides) > - PHP convention is one class-per-file, ergo, following convention > would mean braces are not required anyway. > - Dmitri gets the kudos for introducing PHPs most asked for feature, > instead of 'packages' which no one has asked for. > - The patch introduces naming spaces. at a per-file level. > - Packages suggests a connection between folder structure and file > contents of which there is none. > > Purely from a PR point of view, 'namespaces' is going to be a winner > amongst users and 90% of people will wish for a braces implementation, > while 'packages' is likely to generate more demands for something > called 'namespaces' > -- > Marc Gear > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
