Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:124648
Content-Type: multipart/alternative;
 boundary="------------aclSc4ocKzW0qf2tdUyfELop"
Message-ID: <1052daf1-b00c-4b80-bac1-ebe1b9edaf50@scriptfusion.com>
Date: Sat, 27 Jul 2024 13:57:56 +0100
Precedence: bulk
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: [PHP-DEV] Explicit callee defaults
To: internals@lists.php.net
References: <ab9ded6e-05be-43e7-bafb-f8a81eeba7e9@scriptfusion.com>
 <cdad94a3-fde5-4a4f-913c-f373cf8c33cc@app.fastmail.com>
 <b8b6c953-dc87-4917-802f-f493753f3d4a@scriptfusion.com>
 <0cc6c25f-208e-4782-88c3-c1e3d42454c7@app.fastmail.com>
Content-Language: en-GB
In-Reply-To: <0cc6c25f-208e-4782-88c3-c1e3d42454c7@app.fastmail.com>
From: bilge@scriptfusion.com (Bilge)

This is a multi-part message in MIME format.
--------------aclSc4ocKzW0qf2tdUyfELop
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

On 27/07/2024 13:52, Rob Landers wrote:
> On Sat, Jul 27, 2024, at 11:50, Bilge wrote:
>> On 27/07/2024 10:41, Rob Landers wrote:
>>>
>>> This seems like a case for code generation
>> I don't understand how this has anything to do with code generation. 
>> I understand what composer-attribute-collector is doing, and see no 
>> application for it (or something like it) here. Could you explain a 
>> bit further?
>
> In your example you show how to write code that does what you want, 
> but also that it is annoying to write by-hand. Thus, generating the 
> code instead of writing it by-hand might be better than a new language 
> feature; and there are many things that would benefit from that.
>
> — Rob

I understand your point is that preprocessors could solve this problem, 
and I agree, preprocessors can solve a lot of problems. However, that 
point seems entirely orthogonal to this discussion.

Cheers,
Bilge

--------------aclSc4ocKzW0qf2tdUyfELop
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">On 27/07/2024 13:52, Rob Landers wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:0cc6c25f-208e-4782-88c3-c1e3d42454c7@app.fastmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <title></title>
      <style type="text/css">p.MsoNormal,p.MsoNoSpacing{margin:0}</style>
      <div>On Sat, Jul 27, 2024, at 11:50, Bilge wrote:<br>
      </div>
      <blockquote type="cite" id="qt" style="">
        <div class="qt-moz-cite-prefix">On 27/07/2024 10:41, Rob Landers
          wrote:<br>
        </div>
        <blockquote type="cite"
cite="mid:cdad94a3-fde5-4a4f-913c-f373cf8c33cc@app.fastmail.com">
          <div><br>
          </div>
          <div>This seems like a case for code generation<br>
          </div>
        </blockquote>
        <div>I don't understand how this has anything to do with code
          generation. I understand what composer-attribute-collector is
          doing, and see no application for it (or something like it)
          here. Could you explain a bit further?<br>
        </div>
      </blockquote>
      <div><br>
      </div>
      <div>In your example you show how to write code that does what you
        want, but also that it is annoying to write by-hand. Thus,
        generating the code instead of writing it by-hand might be
        better than a new language feature; and there are many things
        that would benefit from that.</div>
      <div><br>
      </div>
      <div id="sig121229152">— Rob<br>
      </div>
    </blockquote>
    <p>I understand your point is that preprocessors could solve this
      problem, and I agree, preprocessors can solve a lot of problems.
      However, that point seems entirely orthogonal to this discussion.</p>
    <p>Cheers,<br>
      Bilge<br>
    </p>
  </body>
</html>

--------------aclSc4ocKzW0qf2tdUyfELop--