Posted by Rik Wasmus on 09/27/07 01:10

On Thu, 27 Sep 2007 03:02:46 +0200, RageARC <ragearc@gmail.com> wrote:

> I still don't get the point of using nameservers. The fuss that's been
> going on because PHP didn't have support for them is still unclear to
> me. Having functions and classes with the same names, but on different
> containers? What is it useful for? Besides having all MySQL functions
> in a MySQL namespace, SQLite on another, etc... I don't see further
> uses.

Nameservers? I'd almost think you were talking about DNS.

Namespaces on the contrary, are very very good... It ensures different
packages and code can work together, without most of the problems of
clashing function/class/constant names. Often there's similar
functionality within the packages, and developers imagination of what
something should be called is limited (an should be descriptive).

A function called isError for instance is quite common, different
functions in different packages with the same name would cause a fatal
error in php. With namespaces, it would not be a problem (well, as long as
the developer realizes what namespace (s)he's working in).

--
Rik Wasmus

[Back to original message]