Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:100934
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.175 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CALYT1Yo7+54PZrCQN35s1Vf+9QwfS1fau66vmQDH9SE=t2pFfw@mail.gmail.com>
References: <CALYT1Yo7+54PZrCQN35s1Vf+9QwfS1fau66vmQDH9SE=t2pFfw@mail.gmail.com>
Date: Tue, 24 Oct 2017 16:37:58 +0100
Message-ID: <CAPg3XxJEsBxhBCiBMGmroNQDnPsyTCvp3dLV2X-2t7_fiMcCxA@mail.gmail.com>
To: Sammy Kaye Powers <me@sammyk.me>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="94eb2c0820c8aa576a055c4cbb43"
Subject: Re: [PHP-DEV] [RFC] [Discussion] Allow a trailing comma in function calls
From: petercowburn@gmail.com (Peter Cowburn)

--94eb2c0820c8aa576a055c4cbb43
Content-Type: text/plain; charset="UTF-8"

On 7 October 2017 at 19:34, Sammy Kaye Powers <me@sammyk.me> wrote:

> Hello internals friends!
>
> The RFC to allow a trailing comma in function calls is up for discussion:
>
> https://wiki.php.net/rfc/trailing-comma-function-calls
>
> Summary:
>
> - Targets PHP 7.3
> - The previous vote on this combined function calls & declarations in
> the same vote (my bad!)
> - This RFC affects function calls only, not declarations
>

I know it's late in the game, but I have a quick question. This RFC
includes a couple of "Not really a function" functions (namely isset() and
unset()) that will also be able to have a trailing comma, but I'm failing
to find the discussion on including "not really a function" calls in this
RFC. Why were those specific non-functions choices included? Why only those?


> Thanks,
> Sammy Kaye Powers
> sammyk.me
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--94eb2c0820c8aa576a055c4cbb43--