"Yasuo Ohgaki" wrote in message
news:CAGa2bXaMoHDVoZRNNPEEM--km-in4tSyux=tub0paes4tww...@mail.gmail.com...
Hi Tony,
On Thu, Jun 11, 2015 at 4:37 PM, Tony Marston <tonymars...@hotmail.com>
wrote:
"Yasuo Ohgaki" wrote in message
news:CAGa2bXZvuqV4Kwru+wUL-bfTb9_tnv=l16reu-+w+uajx4h...@mail.gmail.com...
Hi Jakub,
On Thu, Jun 11, 2015 at 7:43 AM, Jakub Kubícek <kelerest...@gmail.com>
wrote:
This is weird and ugly what you're fabricating here. The PHP classes
should be all in global namespace. I am really against some
namespacing of them.
It may seems weird if you aren't familiar with languages support
this kind of feature. However, you'll find many languages support
this or similar.
JavaScript is one of them. JavaScript allows to override any functions,
for example. It's works like importing other namespace function into
root. i.e. Provide different feature with the same name.
For long term PHP evolution, having ability to import some namespace
into root namespace is great feature. i.e. API/Module version up. We
can provide both old and new during migration. Use of namespace is
better approach because it may give us super clean global namespace
also.
Regards,
--
Yasuo Ohgaki
yohg...@ohgaki.net
The fact that other languages have this feature should not be a reason to
add it to PHP, especially as it would provide a huge BC break with
absolutely no practical, only theoretical, benefits.
It does not create huge BC.
It's matter of adding a line for namespace or having a default namespace
setting.
Huge or not, it is still a BC break. And what is the benefit in userland?
--
Tony Marston
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
