Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:123751
Feedback-ID: id5114917:Fastmail
Content-Type: multipart/alternative;
 boundary="------------fWWwPqeRSSopENIWX8Cr1bnO"
Message-ID: <86cb8210-a5f5-44d1-9164-21b28aba68a0@rwec.co.uk>
Date: Sat, 22 Jun 2024 18:10:58 +0100
Precedence: bulk
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: [PHP-DEV] [Early Feedback] Pattern matching
To: internals@lists.php.net
References: <2a6b92eb-d5e9-4a1a-9548-a068ac42ebd2@app.fastmail.com>
 <7ec12de5-b2f7-481c-acca-1b38f5be7deb@mabe.berlin>
 <de771d13-eba8-4904-9c92-233fb503d41d@app.fastmail.com>
Content-Language: en-GB
In-Reply-To: <de771d13-eba8-4904-9c92-233fb503d41d@app.fastmail.com>
From: imsop.php@rwec.co.uk ("Rowan Tommins [IMSoP]")

This is a multi-part message in MIME format.
--------------fWWwPqeRSSopENIWX8Cr1bnO
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

On 21/06/2024 19:03, Larry Garfield wrote:
>> * Regex pattern
>>
>> This one is interesting as well ... but I would expect native regex
>> syntax first before introducing it as part of a different RFC. Similar
>> as generics.
> Named capture groups are already part of regex syntax, just not often used.  The example is not introducing anything new there.  (Although Ilija tells me it may be hard to implement, so it may get postponed anyway.  TBD.)


I think what Marc means is that it's weird to see the regex syntax 
outside of a quoted string, since we don't currently have that syntax 
defined in PHP.

It's not even clear what the constraints of that syntax would be; for 
instance, this is valid PHP:

$result = preg_match(subject: $string, pattern: "#
(int|string)
/*(.*/)
#xi");

But I'm guessing it would be a challenge to parse this:

$result = $string is #
(int|string)
/*(.*/)
#xi;

The simple answer is probably to use a more limited syntax, but defining 
that syntax probably deserves its own discussion.


-- 
Rowan Tommins
[IMSoP]

--------------fWWwPqeRSSopENIWX8Cr1bnO
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 21/06/2024 19:03, Larry Garfield
      wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:de771d13-eba8-4904-9c92-233fb503d41d@app.fastmail.com">
      <pre><blockquote type="cite" style="color: #007cff;"><pre
      class="moz-quote-pre" wrap="">* Regex pattern

This one is interesting as well ... but I would expect native regex 
syntax first before introducing it as part of a different RFC. Similar 
as generics.
</pre></blockquote><pre class="moz-quote-pre" wrap="">Named capture groups are already part of regex syntax, just not often used.  The example is not introducing anything new there.  (Although Ilija tells me it may be hard to implement, so it may get postponed anyway.  TBD.)</pre></pre>
    </blockquote>
    <p><br>
    </p>
    <p>I think what Marc means is that it's weird to see the regex
      syntax outside of a quoted string, since we don't currently have
      that syntax defined in PHP. </p>
    <p>It's not even clear what the constraints of that syntax would be;
      for instance, this is valid PHP:<br>
    </p>
    <p>$result = preg_match(subject: $string, pattern: "#<br>
      (int|string)<br>
      /*(.*/)<br>
      #xi");</p>
    <p>But I'm guessing it would be a challenge to parse this:</p>
    <p>$result = $string is #<br>
      (int|string)<br>
      /*(.*/)<br>
      #xi;</p>
    <p>
    </p>
    The simple answer is probably to use a more limited syntax, but
    defining that syntax probably deserves its own discussion.<br>
    <p><br>
    </p>
    <pre class="moz-signature" cols="72">-- 
Rowan Tommins
[IMSoP]</pre>
  </body>
</html>

--------------fWWwPqeRSSopENIWX8Cr1bnO--