Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:76212
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.53 as permitted sender)
MIME-Version: 1.0
Sender: yohgaki@gmail.com
Date: Mon, 28 Jul 2014 11:58:48 +0900
Message-ID: <CAGa2bXYqHCSvatYHoc2j48eqc2oMG6XwOOUxdOFxuvB6eZHiuw@mail.gmail.com>
To: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a1133c20a8a7ad204ff381c6b
Subject: "PHP" namespace?
From: yohgaki@ohgaki.net (Yasuo Ohgaki)

--001a1133c20a8a7ad204ff381c6b
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi all,

Since we have discussion for Next PHP, "PHP" namespace discussion would be
nice
to have.

Currently, PHP module functions/classes/interfaces are using global(root)
namespace.
If it is changed to use its own namespace, user space APIs may be changed
flexible and user controlled manner. Thus, PHP may have

 - Consistent naming
 - Consistent parameter order
 - Graceful function/class/interface deprecation
(We know what we should do for these, right?)

without much compatibility issues.


"PHP" namespace may be used to provide PHP(and 3rd party)
functions/classes/interfaces/constants.
"PHP\Legacy" (or whatever) may be used for legacy
functions/classes/interfaces/constants.

From PHP 5.6, userland function aliasing can be done with namespace.
Following code overrides existing function.

<?php
use function \mb_strlen as strlen;
var_dump(strlen('=E6=97=A5=E6=9C=AC=E8=AA=9E'));
?>

Result:
int(3)

It's good to use prefered API, but it requires "use" for every function
APIs to be overridden.
Note: Classes/Interfaces may override by "use" one by one also.

With "PHP" and "PHP\Legacy" namespace, user may write:

<?php
namespace PHP; // Use current PHP functions/classes/interfaces/constants

// Code uses current API
?>

<?php
namespace PHP;
namespace PHP\Legacy; // Override with legacy PHP
functions/classes/interfaces/constants.

// Code uses legacy API
?>

For compatibility, default namespace setting would be nice to have.
  - None for compiled default
  - "PHP" for php.ini-*

Previous example codes became:

<?php
// Code uses current API
?>

<?php
namespace PHP\Legacy; // Override with legacy PHP
functions/classes/interfaces/constants.
// Code uses legacy API
?>

Issue would be codes that assume PHP functions/classes/interfaces/constants
are
defined in global(root) namespace. (e.g. \strlen()) This could be
workaround by allowing
"use"  aliasing to global(root) namespace. (e.g. "use PHP\Legacy as \;") In
this case,
current functions/classes/interfaces may stay in global(root) namespace.
(or "use PHP as \;")


Programmers may shoot their own foot by this. This is the trade off of
flexibility.

Any thoughts and/or comments?

Regards,

--
Yasuo Ohgaki
yohgaki@ohgaki.net

--001a1133c20a8a7ad204ff381c6b--