"Conflict Between Namespaced Functions and static class methods"
I think #3 ("use namespace" or "use class") makes the most sense. I assume if
there is a conflict without being explicit it would give an error? I also
assume in the even of no conflict you can still just say "use foo" and will
assume namespace, right? If so that seems to be very clear. Regarding the
potential __autoload performance problem, how big are we talking?
"Resolving access to internal classes"
I think your suggestion of changing the order around makes perfect sense.
All that said, I want to personally thank-you Greg for getting us to focus on
the real issues, not the politics around it.
--Tony
----- Original Message ----
From: Greg Beaver <[EMAIL PROTECTED]>
To: PHP Developers Mailing List <internals@lists.php.net>
Sent: Wednesday, October 15, 2008 3:35:11 PM
Subject: [PHP-DEV] my last attempt at sanity with namespaces
Hi,
http://wiki.php.net/rfc/namespaceissues
Read it and discuss. Let's be clear people: the technical problems in
namespaces are limited and solvable. The problems in the political
environment surrounding them may not be. Wouldn't politics be a
stupid-ass reason to remove namespaces?
Greg
--
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
