1) Lack of cohesiveness of name resolution rules
Why is this an argument against: name resolution rules with namespaces
change completely the way names are resolved in PHP.
How does it affects: this breaks the explicitness of names in PHP. It will
affect code debugging and review.
Example:
Su
a) Introduce a special name to refer to the current namespace (as self::
works for the current class).
namespace::
> All namespace access should be explicit:
Consequence: nobody uses namespaces, as it's too annoying.
b) Name aliasing with use should only generate namespaces aliases:
See n
2007/12/10, Stanislav Malyshev <[EMAIL PROTECTED]>:
>
> > All namespace access should be explicit:
>
> Consequence: nobody uses namespaces, as it's too annoying.
Putting $this-> and self:: is annoying , that didn't stop anybody from using
objects in PHP.
> b) Name aliasing with use should only g
2007/12/10, Martin Alterisio <[EMAIL PROTECTED]>:
>
>
> > 2) Using :: as namespace separator generates ambiguity
> >
> > Would that be 20th reincarnation of "let's find weirdest namespace
> > separator" thread? :)
>
>
> Please no. Just find the right one.
>
PS: Wasn't : (one colon) used as namespa
2007/12/10, Martin Alterisio <[EMAIL PROTECTED]>:
>
>
> > c) If bracketed namespaces are a no-go, consider the possibility of
> > > declaring the full name of the namespaced element in its definition:
> >
> > Which would lead to people routinely mixing different namespaces inside
> > one file. Bad
Agreed. I don't see any point in this limitation. As for confusion,
debugging would not be too hard (just echo __NAMESPACE__), or brackets
would solve that problem.
On Mon, 2007-12-10 at 16:59 -0300, Martin Alterisio wrote:
> 2007/12/10, Martin Alterisio <[EMAIL PROTECTED]>:
> >
> >
> > > c) If br
