Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:66037
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.160.49 as permitted sender)
References: <1361344921.21988.YahooMailClassic@web171605.mail.ir2.yahoo.com> <51247F6C.5040309@oracle.com>
In-Reply-To: <51247F6C.5040309@oracle.com>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii
Message-ID: <D2BFFFA1-235F-4F78-8928-0A4FE13A4BA7@gmail.com>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Date: Wed, 20 Feb 2013 01:41:07 -0800
To: Klaus Ufo <klausufo@yahoo.fr>
Subject: Re: [PHP-DEV] PHP 6 : a new API ?
From: mike503@gmail.com (Michael Shadle)


On 02/19/2013 11:22 PM, Klaus Ufo wrote:
> Hi there !
>=20
> We all know that the current PHP API has flaws. Maybe we could use namespa=
ces to build a new coherent PHP API ? Like :
>=20
> - \arr
> - \num
> - \str
>=20
> and so on. Advantages :
>=20
> - no more global functions
> - separation of concerns
> - backward compatibility
> - work can be done progressively
> - easy to add user-defined functions (using php namespaces)
> - we could provide a \str\utf8 namespace
>=20
> This is just an idea. I don't know what is your vision for a next PHP 6.
>=20
> KH
>=20


I'm aware people complain about PHP flaws, but having misc global core funct=
ions for strings, arrays and other data types is a new one.

I am still a purest at heart and don't see the need for namespacing in gener=
al. I am thinking it provides some lower level memory space improvements and=
 less conflicts, but I feel like if you can't code in global space perhaps y=
ou should be rethinking how you code. I don't think most people care about t=
he lower level advantages, they're just looking at it from a code laziness p=
erspective.

Why make \bar\baz\foo() or $bar->baz->foo() instead of bar_baz_foo()? Prefix=
ing functions seems perfectly effective. I see a lot of code that looks like=
 they're using namespaces or OO just to group things together and organize c=
ode in some fashion. Not because there's any inherent benefit.

I'd much rather see effort taken on renaming functions to be more consistent=
, and making needle/haystack consistent, and maybe throw in named parameters=
. PHP is getting too complex as it is.

Signed,
PHP purest at heart, (who has code that has lasted for a decade and multiple=
 major php code changes still did not break it)=