Lester Caine wrote:
The backslash is not ideal, but I think we all need to get behind it
rather than complaining. The only other real alternative today is to
shelve namespaces altogether for the next release rather than putting
something in that is simply not practical to extend later?
I'd pref
x27;t like.
You just live with that or chouse another language. That's all.
2008/10/27 Thomas Lee <[EMAIL PROTECTED]>
Lester Caine wrote:
The backslash is not ideal, but I think we all need to get behind it
rather than complaining. The only other real alternative today is to shelv
Steph Fox wrote:
Hi Thomas,
Anyway, my point is that there may be other options. Such as putting
off a long-sought feature until it can be implemented properly.
OK, since you obviously didn't do any background reading before
posting to this list, let me direct you to the history behind this
David Grudl wrote:
But what is the purpose of namespaces? To give developers their own
separated space. And it is their responsibility to not use ambiguous
names. PHP has not problem with class Foo::Bar and namespace Foo::Bar,
but coding standards usually prohibits it.
+1 to that.
Cheers,
