Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:85368
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.171 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <011c01d063d4$34b4dff0$9e1e9fd0$@php.net>
References: <CAJ97eO3=1YbfLAK2tY-zLpWMdr6DrkE_0nehykWA7LnQa_Cx2w@mail.gmail.com>
	<011c01d063d4$34b4dff0$9e1e9fd0$@php.net>
Date: Sat, 21 Mar 2015 16:42:59 +0300
Message-ID: <CAJ97eO3PkT_Wpg1Ldx+cGvrfvWUP_R70aUDkVn3hZY2zupUMLg@mail.gmail.com>
To: francois@php.net
Cc: internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11c2fb4c73c0e20511cc9ce3
Subject: =?UTF-8?Q?Re=3A_=5BPHP=2DDEV=5D_Ten_years_estimated_Plan_to_replace_PH?=
	=?UTF-8?Q?P=E2=80=99s_inconsistent_API?=
From: nathan.o.wesley@gmail.com (Nathan wesley)

--001a11c2fb4c73c0e20511cc9ce3
Content-Type: text/plain; charset=UTF-8

>
> I think that, while attractive, using the same syntax for object methods
> and scalar 'pseudo-'methods is too ambiguous. We just need to solve two
> issues : intuitive order of arguments and nested call readability. We don't
> need to implement the whole OO stuff for scalars. Except this detail, no
> limitation IMO.
>
>
if you're going to write  API for string manipulation for example you want
it either Object Oriented or procedural style. because the API should be
fluent method chaining etc. you don't want to stop the chain and wrap it
with a function call. (just my opinion) these things needs to be discussed
if the internals are willing to do it. it will happen !

i'm completely sure the many developers will support the new API and all of
them are willing to help.

i wrote some code imagining that we have the new API. PHP will just be so
beautiful it will be a HUGE success.


Regards

--001a11c2fb4c73c0e20511cc9ce3--