ID:               46943
 Updated by:       johan...@php.net
 Reported By:      hostit at mail dot ru
-Status:           Open
+Status:           Bogus
 Bug Type:         Feature/Change Request
 Operating System: All
 PHP Version:      5.3.0alpha3
 New Comment:

Believe me, we invested time (=mone, according to your equation) into
PHP, too :-)


Previous Comments:
------------------------------------------------------------------------

[2008-12-26 13:31:33] hostit at mail dot ru

Description:
------------
Hello.

As you might know a fairly large amount of PHP developers think that
backslash (\) is an inappropriate symbol for namespace separator.
[http://blogsearch.google.com/blogsearch?hl=en&q=php%20namespace%20separator&um=1&ie=UTF-8&sa=N&tab=wb]

Two main reasons are:
1. It's ugly. (Indeed.)
2. Confusion with escaping.

As the roar strengthens, it's starting to appear that it might be one
of the nails in the PHP coffin. Just look at the amount of FUD spread 
because of this damned backslash...

For us, the PHP developers, it's very dangerous tendency, because we
have invested a lot of our time (read: money) into PHP software.

Please, please, PLEASE reconsider that. I understand the problems with 
"::", but I think there can be a solution - to throw fatal error when
there's a conflict between static method name and the function in a
namespace. (You can't declare two functions/classes with the same name,
can you? And it is logical and expected behavior.) I'm sure it will make
PHP programmers happy.

As it's still alpha, the change is possible. And the mistake in the
design of the language will remain forever after the release.


THANK YOU!

Reproduce code:
---------------
\This\is::ugly()

Expected result:
----------------
::This::looks::better()

Actual result:
--------------
\This\is::ugly()


------------------------------------------------------------------------


-- 
Edit this bug report at http://bugs.php.net/?id=46943&edit=1

Reply via email to