Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:122942
Content-Type: multipart/alternative;
 boundary="------------87gBhugWLLCp47AgsoMFrkQY"
Message-ID: <07d3168c-f8dc-4b2c-9eef-eacef8a0812c@uzy.me>
Date: Thu, 4 Apr 2024 23:00:16 +0200
Precedence: bulk
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: [PHP-DEV] RFC idea: using the void type to control maximum arity
 of user-defined functions
To: internals@lists.php.net
References: <6299b649-c19b-4172-9632-2ef0a55d256d@uzy.me>
 <CA+pig-JBkZip5bEM0gSwcwNRO9NDKuRO2vu=iHnx2diBTv9Bng@mail.gmail.com>
 <7B32AF65-CA40-40F5-BA59-CB5180EC4D7F@gmail.com>
 <8f71d807-78e6-49f6-acc7-b1fc09d815ba@uzy.me>
 <989e3e13-48ee-4970-8485-f79bb70ad37c@bastelstu.be>
Content-Language: fr
In-Reply-To: <989e3e13-48ee-4970-8485-f79bb70ad37c@bastelstu.be>
From: r@uzy.me (Pablo Rauzy)

This is a multi-part message in MIME format.
--------------87gBhugWLLCp47AgsoMFrkQY
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

Le 04/04/2024 à 17:57, Tim Düsterhus a écrit :
> Hi
>
> On 4/4/24 16:36, Pablo Rauzy wrote:
>> I strongly agree in theory, but this could break existing code, and
>> moreover such a proposal was already rejected:
>> https://wiki.php.net/rfc/strict_argcount
>
> The RFC is 9 years old by now. My gut feeling is be that using an 
> actual variadic parameter for functions that are variadic is what 
> people do, because it makes the function signature much clearer. 
> Actually variadic parameters are available since PHP 5.6, which at the 
> time of the previous RFC was the newest version. Since then we had two 
> major releases, one of which (7.x) is already out of support.
>
> I think it would be reasonable to consider deprecating passing extra 
> arguments to a non-variadic function.

Well, if there is a consensus to agree on that, it would be even better!

Cheers,

-- 
Pablo

--------------87gBhugWLLCp47AgsoMFrkQY
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<!DOCTYPE html>
<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <div class="moz-cite-prefix">Le 04/04/2024 à 17:57, Tim Düsterhus a
      écrit :<br>
    </div>
    <blockquote type="cite"
      cite="mid:989e3e13-48ee-4970-8485-f79bb70ad37c@bastelstu.be">Hi
      <br>
      <br>
      On 4/4/24 16:36, Pablo Rauzy wrote:
      <br>
      <blockquote type="cite">I strongly agree in theory, but this could
        break existing code, and
        <br>
        moreover such a proposal was already rejected:
        <br>
        <a class="moz-txt-link-freetext" href="https://wiki.php.net/rfc/strict_argcount">https://wiki.php.net/rfc/strict_argcount</a>
        <br>
      </blockquote>
      <br>
      The RFC is 9 years old by now. My gut feeling is be that using an
      actual variadic parameter for functions that are variadic is what
      people do, because it makes the function signature much clearer.
      Actually variadic parameters are available since PHP 5.6, which at
      the time of the previous RFC was the newest version. Since then we
      had two major releases, one of which (7.x) is already out of
      support.
      <br>
      <br>
      I think it would be reasonable to consider deprecating passing
      extra arguments to a non-variadic function.
      <br>
    </blockquote>
    <p>Well, if there is a consensus to agree on that, it would be even
      better!<br>
    </p>
    Cheers,<br>
    <pre class="moz-signature" cols="72">-- 
Pablo</pre>
  </body>
</html>

--------------87gBhugWLLCp47AgsoMFrkQY--