Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:122931
Content-Type: multipart/alternative;
 boundary="------------7ZUzwU8RKd0o0ADqwF6GeCGl"
Message-ID: <2f3349e7-f10a-4907-844e-84e0b35f0fee@uzy.me>
Date: Thu, 4 Apr 2024 15:19:51 +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>
 <CAGBsUrdiyxgO5Ss0dCos53bsgzZ2TJMUe0R1e0_zgFzHxU1cZg@mail.gmail.com>
Content-Language: fr
In-Reply-To: <CAGBsUrdiyxgO5Ss0dCos53bsgzZ2TJMUe0R1e0_zgFzHxU1cZg@mail.gmail.com>
From: r@uzy.me (Pablo Rauzy)

This is a multi-part message in MIME format.
--------------7ZUzwU8RKd0o0ADqwF6GeCGl
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

Hello Kamil,

Le 04/04/2024 à 15:10, Kamil Tekiela a écrit :
> Interesting proposal, but immediately I have two questions:
> 1. Why is passing extra arguments a problem at all? Is generating a
> warning a good idea? If you would like to introduce a new syntax to
> enforce non-variadic functions, shouldn't it be a runtime error then?
> Generating a warning makes it look like the new syntax still allows
> for variadic arguments, but passing the extra arguments now is somehow
> a bad thing to do.
> 2. How does this affect func_get_args()? Will the function stop
> working or continue working as before?

1. Indeed, if implemented it should be an error rather than a warning, 
you're right.

2. I don't see why func_get_args() should work differently, but that 
maybe my lack of knowledge of the internals of PHP. In any case I think 
it would be better if it worked the same.

Regards,

-- 
Pablo

--------------7ZUzwU8RKd0o0ADqwF6GeCGl
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">Hello Kamil,</div>
    <div class="moz-cite-prefix"><br>
    </div>
    <div class="moz-cite-prefix">Le 04/04/2024 à 15:10, Kamil Tekiela a
      écrit :<br>
    </div>
    <blockquote type="cite"
cite="mid:CAGBsUrdiyxgO5Ss0dCos53bsgzZ2TJMUe0R1e0_zgFzHxU1cZg@mail.gmail.com">
      <pre class="moz-quote-pre" wrap="">Interesting proposal, but immediately I have two questions:
1. Why is passing extra arguments a problem at all? Is generating a
warning a good idea? If you would like to introduce a new syntax to
enforce non-variadic functions, shouldn't it be a runtime error then?
Generating a warning makes it look like the new syntax still allows
for variadic arguments, but passing the extra arguments now is somehow
a bad thing to do.
2. How does this affect func_get_args()? Will the function stop
working or continue working as before?</pre>
    </blockquote>
    <p><span style="white-space: pre-wrap">1. Indeed, if implemented it should be an error rather than a warning, you're right.</span></p>
    <p><span style="white-space: pre-wrap">2. I don't see why func_get_args() should work differently, but that maybe my lack of knowledge of the internals of PHP. In any case I think it would be better if it worked the same.</span></p>
    <p><span style="white-space: pre-wrap">Regards,
</span><span style="white-space: pre-wrap">
</span></p>
    <pre class="moz-signature" cols="72">-- 
Pablo</pre>
  </body>
</html>

--------------7ZUzwU8RKd0o0ADqwF6GeCGl--