Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:76243
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.218.47 as permitted sender)
MIME-Version: 1.0
Sender: morrison.levi@gmail.com
In-Reply-To: <CAGa2bXYqHCSvatYHoc2j48eqc2oMG6XwOOUxdOFxuvB6eZHiuw@mail.gmail.com>
References: <CAGa2bXYqHCSvatYHoc2j48eqc2oMG6XwOOUxdOFxuvB6eZHiuw@mail.gmail.com>
Date: Mon, 28 Jul 2014 19:49:36 -0600
Message-ID: <CAFMT4NoYNTYTGDRteYZ5rYYythhbPH-oeDS49S_eF9q0=RK-OQ@mail.gmail.com>
To: Yasuo Ohgaki <yohgaki@ohgaki.net>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] "PHP" namespace?
From: levim@php.net (Levi Morrison)

> 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?)

I do not support it for consistent naming or parameter order by
themselves; this would likely create more confusion.

However I see value in creating new APIs for certain operations such
as sorting, mapping, reducing and filtering. These new APIs could work
on both arrays and traversables and provide a more cohesive API. This
would 'fix' several bug reports dealing with array functions that you
can't pass traversables or array-like objects to where you would
reasonably expect to be able to. When creating these functions we
could be careful to create consistent naming conventions and
consistent parameter orders, but again I consider this a side-effect
rather than a reason.