Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:85408 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 65292 invoked from network); 22 Mar 2015 10:50:15 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 22 Mar 2015 10:50:15 -0000 Authentication-Results: pb1.pair.com smtp.mail=francois@php.net; spf=unknown; sender-id=unknown Authentication-Results: pb1.pair.com header.from=francois@php.net; sender-id=unknown Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 212.27.42.2 as permitted sender) X-PHP-List-Original-Sender: francois@php.net X-Host-Fingerprint: 212.27.42.2 smtp2-g21.free.fr Received: from [212.27.42.2] ([212.27.42.2:36122] helo=smtp2-g21.free.fr) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id F2/F8-00828-56E9E055 for ; Sun, 22 Mar 2015 05:50:14 -0500 Received: from moorea (unknown [82.240.16.115]) by smtp2-g21.free.fr (Postfix) with ESMTP id 4B5D14B008E; Sun, 22 Mar 2015 11:48:44 +0100 (CET) Reply-To: To: "'Nathan wesley'" Cc: "'internals'" References: <011c01d063d4$34b4dff0$9e1e9fd0$@php.net> In-Reply-To: Date: Sun, 22 Mar 2015 11:50:02 +0100 Message-ID: <003401d0648d$f3a8b2b0$dafa1810$@php.net> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQJ0U/6rqO3FVP5oK2SGL8/QaQsyzwEjcPRpAkgHD1qbxRXfAA== Content-Language: fr X-Antivirus: avast! (VPS 150322-0, 22/03/2015), Outbound message X-Antivirus-Status: Clean Subject: =?utf-8?Q?RE:_=5BPHP-DEV=5D_Ten_years_estimate?= =?utf-8?Q?d_Plan_to_replace_PHP=E2=80=99s_inconsis?= =?utf-8?Q?tent_API?= From: francois@php.net (=?utf-8?Q?Fran=C3=A7ois_Laupretre?=) >De : Nathan wesley [mailto:nathan.o.wesley@gmail.com]=20 > > if you're going to write API for string manipulation for example you = want it either Object Oriented or procedural style.=20 > 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 ! =20 What I meant is that we need a syntax that allows unambiguous parameter = order and chained calls but we probably shouldn't use the '->' operator = for scalars. The main reason is that it would make code harder to = understand, but there are other reasons (like function receiving object = arguments). Regards Fran=C3=A7ois