Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:72763
Return-Path: <ingwie2000@googlemail.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 15481 invoked from network); 22 Feb 2014 21:42:52 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 22 Feb 2014 21:42:52 -0000
Authentication-Results: pb1.pair.com smtp.mail=ingwie2000@googlemail.com; spf=pass; sender-id=pass
Authentication-Results: pb1.pair.com header.from=ingwie2000@googlemail.com; sender-id=pass
Received-SPF: pass (pb1.pair.com: domain googlemail.com designates 74.125.83.54 as permitted sender)
X-PHP-List-Original-Sender: ingwie2000@googlemail.com
X-Host-Fingerprint: 74.125.83.54 mail-ee0-f54.google.com  
Received: from [74.125.83.54] ([74.125.83.54:34622] helo=mail-ee0-f54.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id 5F/10-12844-BD919035 for <internals@lists.php.net>; Sat, 22 Feb 2014 16:42:52 -0500
Received: by mail-ee0-f54.google.com with SMTP id c41so1449796eek.13
        for <internals@lists.php.net>; Sat, 22 Feb 2014 13:42:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=googlemail.com; s=20120113;
        h=content-type:mime-version:subject:from:in-reply-to:date:cc
         :content-transfer-encoding:message-id:references:to;
        bh=KDZmvFFdxF1UUJxaWNz7YngKJInpHq/VPfVglFhkNaM=;
        b=TLiYgYlGDwywMtJVN6D/POyMH6UEorYc/pPUP/XwM+DfwyYbDos822Kxd5oRvWrAzE
         wlg0GczyDxTcsS9lTbV4OkbN+TPjLqdtUAiz4sG0+gXZgfmudfa0z0TFNq//SH9ImpTu
         I8eg+9Ub1qWWECYfyDNLbFKFwNv+BzbqX7BLOviQTgMvuLdj9wSpD8BljBDCJ03zLTgb
         Aj9HY41q/KKOu63/DP64mGtBTIjC/8OSOqsQnUtLtCuTDeO3HiR8ItjDcrkmroi2Yo56
         4NMYvwNi2nsf2BPOVQlj4YIVWwLWnKI3iLIWb1hzba523huAdZvPx+zd8EjJ01pqIb5B
         wApw==
X-Received: by 10.15.41.140 with SMTP id s12mr16430633eev.4.1393105368861;
        Sat, 22 Feb 2014 13:42:48 -0800 (PST)
Received: from ingwies-air.fritz.box (p5B15D5B6.dip0.t-ipconnect.de. [91.21.213.182])
        by mx.google.com with ESMTPSA id j41sm43349686eey.15.2014.02.22.13.42.47
        for <multiple recipients>
        (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
        Sat, 22 Feb 2014 13:42:48 -0800 (PST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1822\))
In-Reply-To: <4283043.OsXFhf6CrZ@rofl>
Date: Sat, 22 Feb 2014 22:42:48 +0100
Cc: internals <internals@lists.php.net>,
 Andrea Faulds <ajf@ajf.me>,
 Gleb Golubitsky <sectoid@gnolltech.org>,
 Christopher Jones <christopher.jones@oracle.com>,
 Nikita Popov <nikic@php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <3F5F2F92-33B0-4A27-8762-C0132058A657@googlemail.com>
References: <3930601.eOsJ67jUeD@dagon> <3095034.S38469PJ60@dagon> <CA0C1888-942C-4461-997D-1CB976F13A01@ajf.me> <4283043.OsXFhf6CrZ@rofl>
To: Patrick Schaaf <php@bof.de>
X-Mailer: Apple Mail (2.1822)
Subject: Re: [PHP-DEV] Named params status
From: ingwie2000@googlemail.com (Kevin Ingwersen)


Am Sa. Feb. 22 2014 17:15:20 schrieb Patrick Schaaf:

> On Saturday 22 February 2014 14:25:07 Andrea Faulds wrote:
>> On 21 Feb 2014, at 19:49, Gleb Golubitsky <sectoid@gnolltech.org> =
wrote:
>>> Sad to hear so. What exactly stops from having it in the mainline?
>>=20
>> While the named parameters implementation works, we'd need to update =
the
>> function info headers for every single internal function, and make =
sure it
>> matches the documentation. I think Nikita simply doesn=92t have the =
time on
>> his hands.
>=20
> I know that I said it more nicely before.... That is stupidity.
>=20
> Just release the feature for user code (self-written functions and =
methods).
>=20
> Create a suitable variation of the internals function declaration =
macros that=20
> expresses "this function has been vetted for named parameter usage, =
and refuse=20
> to accept named parameters (FATAL) for any function not so vetted.
>=20
> Then let the internal function vetting proceed at whatever pace it =
takes,=20
> later.
>=20
> If you first wait for each and every internal (and extension?) =
function being=20
> converted, this will never happen.
>=20
> best regards
>  Patrick


I agree with that post. For most, we can just create our own wrapper =
functions untill the functions have a real named parameter =
implementation (has_named_params() ?). The named parameters can then be =
added from time to time over minimal releases (5.6.?).=