I've missed out on most of this discussion via email, bit I've watching the
threads anyway. It seems to me the main debate is about backwards
compatibility, and where the classes belong.
My reason for starting this thread was not really out of necessity, but
merely to argue semantics. So if it
2015-06-12 10:10 GMT+02:00 Tony Marston tonymars...@hotmail.com:
And what is the benefit in userland?
That is the question.
I think clean global namespace isn't enough argument, we can exist in
the current situation and considering the fact that most of the new
PHP applications have their own
Hi,
2015-06-15 16:09 GMT+02:00 Jakub Kubíček kelerest...@gmail.com:
I think clean global namespace isn't enough argument, we can exist in
the current situation and considering the fact that most of the new
PHP applications have their own namespaces, it could probably make
more sense to
Sebastian B.-Hagensen wrote:
On an unrelated note:
http://php.net/manual/en/userlandnaming.tips.php should hint towards
real namespaces.
There is already a respective ticket:
https://bugs.php.net/bug.php?id=69369. :)
--
Christoph M. Becker
--
PHP Internals - PHP Runtime Development
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
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
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
/cc-ing internals, as I sent the message privately to Yasuo by mistake.
-- Forwarded message --
From: Jakub Kubíček kelerest...@gmail.com
Date: 2015-06-11 0:40 GMT+02:00
Subject: Re: [PHP-DEV] Migrating PHP classes to built in namespace
To: Yasuo Ohgaki yohg...@ohgaki.net
Hi
Hi Jakub,
On Thu, Jun 11, 2015 at 7:43 AM, Jakub Kubíček 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
Hi Marc,
On Thu, Jun 4, 2015 at 6:04 PM, Marc Bennewitz dev@mabe.berlin wrote:
This one is not compatible with current code as you have to alias the PHP
namespace to the root one before using full classes like \DateTime.
Right.
We are better to have PHP namespace for internal
On 06/04/2015 10:01 AM, Yasuo Ohgaki wrote:
Hi all,
On Thu, Jun 4, 2015 at 12:07 AM, Sara Golemon poll...@php.net wrote:
On Wed, Jun 3, 2015 at 1:33 AM, Dominic Grostate
codekest...@googlemail.com wrote:
Has there been any discussion or consideration towards migrating or at
least aliasing
Hi all,
On Thu, Jun 4, 2015 at 12:07 AM, Sara Golemon poll...@php.net wrote:
On Wed, Jun 3, 2015 at 1:33 AM, Dominic Grostate
codekest...@googlemail.com wrote:
Has there been any discussion or consideration towards migrating or at
least aliasing all built in classes to a Php vendor
Dominic Grostate wrote on 03/06/2015 09:33:
Hi,
I couldn't find any information on this elsewhere, or perhaps I didn't look
hard enough. Its been bugging me a while though so I though I would ask.
Has there been any discussion or consideration towards migrating or at
least aliasing all built
AFAIK the PHP namespace is the root one.
Lorenzo
2015-06-03 10:33 GMT+02:00 Dominic Grostate codekest...@googlemail.com:
Hi,
I couldn't find any information on this elsewhere, or perhaps I didn't look
hard enough. Its been bugging me a while though so I though I would ask.
Has there been
Yes, however for consistency, I personally like the idea of using a longer
namespace over prefixed class names. The most relevant example being the
SPL data structures.
For instance SplStack might come under Php\Collection\Stack.
As far as I can tell there is a fair amount of fear of adding new
Hi,
I couldn't find any information on this elsewhere, or perhaps I didn't look
hard enough. Its been bugging me a while though so I though I would ask.
Has there been any discussion or consideration towards migrating or at
least aliasing all built in classes to a Php vendor namespace?
For
On Wed, Jun 3, 2015 at 1:33 AM, Dominic Grostate
codekest...@googlemail.com wrote:
Has there been any discussion or consideration towards migrating or at
least aliasing all built in classes to a Php vendor namespace?
Not any that's led to a consensus.
Personally, I like the idea of moving
17 matches
Mail list logo
