Kalle Sommer Nielsen wrote:
Hi
Like Guilherme wrote, I've spend alot of my day reading the emails and
trying to understand the namespace issues and after reading your
proposal I understand the issues you're bringing up. So heres my
votes:
Conflict between namespaced functions and static class methods:
I don't think it makes much sense to be able to make a class inside a
namespace with the same name as another namespace, so my +1 here goes
to option #4 (disallow mixing namespaces and classes with the same
name).
Resolving access to internal classes:
I'm a +1 for changing the resolution order.
Cheers,
Kalle Sommer Nielsen
out of the four options I'm:
+1 to (disallow mixing namespaces and classes with the same name)
+5 to changing the :: namespace operator personally I like period(.)
IMO
::: is visually and legibly dire
you can't namespace::class:::static_method() [or change the
class::static() operator at all] as that would mean every reference to a
static method in a class since eternity was using the wrong operator
"use namespace"/"use class" syntax seems to bloat but certainly isn't
disambiguous
or use something completely mad like uri scheme's for namespaces!
ns://one/step/two()
ns://one/step::two()
[the last comment should probably be disregarded]
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
