Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:86478
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: softfail (pb1.pair.com: domain golemon.com does not designate 209.85.217.175 as permitted sender)
MIME-Version: 1.0
Sender: php@golemon.com
In-Reply-To: <CAFKaYMoPMh7=kw++S=0JYDx86aKEMg=e8ymhWRyPxv1V8ugQcw@mail.gmail.com>
References: <CAFKaYMoPMh7=kw++S=0JYDx86aKEMg=e8ymhWRyPxv1V8ugQcw@mail.gmail.com>
Date: Wed, 3 Jun 2015 08:07:34 -0700
Message-ID: <CAESVnVonWgC519nAVka+6HJLM9iNJPMw55a9FEq+CwnZuoC2dA@mail.gmail.com>
To: Dominic Grostate <codekestrel@googlemail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] Migrating PHP classes to built in namespace
From: pollita@php.net (Sara Golemon)

On Wed, Jun 3, 2015 at 1:33 AM, Dominic Grostate
<codekestrel@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 EVERYTHING to PHP\ at once and
building in an automatic fallback, so an app could do:

<?php
$dt = new DateTime(...); // uses builtin DataTime via fallback to PHP namespace

Or:

<?php
class DateTime { ... }
$mydt = new DateTime(...); // Uses user supplied DateTime
$pdt = new PHP\DateTime(...); // Uses builtin DateTime

Possibly paired with the ability to import a NS to root:

<?php
use PHP as \;
$pdt = new DateTime(...); // Uses builtin DateTime from root namespace

I don't feel strongly about any of this though, so I'm not personally
inclined to push any RFC to make it happen.

-Sara