Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:104816 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 68846 invoked from network); 20 Mar 2019 11:09:05 -0000 Received: from unknown (HELO vie01a-dmta-pe07-1.mx.upcmail.net) (84.116.36.17) by pb1.pair.com with SMTP; 20 Mar 2019 11:09:05 -0000 Received: from [172.31.216.235] (helo=vie01a-pemc-psmtp-pe12.mail.upcmail.net) by vie01a-dmta-pe07.mx.upcmail.net with esmtp (Exim 4.88) (envelope-from ) id 1h6W9f-0003BH-3N for internals@lists.php.net; Wed, 20 Mar 2019 09:00:55 +0100 Received: from mail02.home ([213.47.8.56]) by vie01a-pemc-psmtp-pe12.mail.upcmail.net with ESMTP id 6W8hhI4NnxLwq6W8hh3wdo; Wed, 20 Mar 2019 08:59:55 +0100 X-Env-Mailfrom: markus@fischer.name X-Env-Rcptto: internals@lists.php.net X-SourceIP: 213.47.8.56 X-CNFS-Analysis: v=2.3 cv=WaxylHpX c=1 sm=1 tr=0 a=UsP8JIz990cEySE/ILGzbQ==:117 a=UsP8JIz990cEySE/ILGzbQ==:17 a=jpOVt7BSZ2e4Z31A5e1TngXxSK0=:19 a=IkcTkHD0fZMA:10 a=xqWC_Br6kY4A:10 a=MKtGQD3n3ToA:10 a=1oJP67jkp3AA:10 a=NTGMnVQrEZIA:10 a=2EALvoLjsrEA:10 a=ZZnuYtJkoWoA:10 a=7LT1oxbXRdmKNfgIhUoA:9 a=QEXdDO2ut3YA:10 Received: from mail02.home ([192.168.1.14] helo=[IPv6:::1]) by mail02.home with esmtp (Exim 4.72) (envelope-from ) id 1h6W8g-0002Ji-Db for internals@lists.php.net; Wed, 20 Mar 2019 08:59:54 +0100 To: internals@lists.php.net References: Message-ID: <5ff02d2c-2b20-b6bb-0a65-b1d6f1305f71@fischer.name> Date: Wed, 20 Mar 2019 09:03:24 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.5.3 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Spam_score: -2.9 X-Spam_score_int: -28 X-Spam_bar: -- X-Spam_report: Spam detection software, running on the system "scanner01.home", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: On 19.03.19 15:58, Nikita Popov wrote: > I'm wondering if we shouldn't consider a new object oriented API for PCRE > which can return a match object where subpattern positions and contents can > be queried via method calls, so you only pay for the parts that you do > access. [...] Content analysis details: (-2.9 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] X-CMAE-Envelope: MS4wfFJGBxSJN0aVGpaB+/V/Sy9Lk7deCDvF3ggBnh4+8WylvCoVlVQvB9mQ1o6q1cjOz6Y440/fLVPs4pIdtJYyZ+L1YBmD+j/3idVzQ+vTrDpyBxNDz1Tv ST4fIpwJfiiI5iJHHKh7729GdmYZJTaV6mz/30UzXean8X1oFCz4IfA7 Subject: Re: [PHP-DEV] Offset-only results from preg_match From: markus@fischer.name (Markus Fischer) On 19.03.19 15:58, Nikita Popov wrote: > I'm wondering if we shouldn't consider a new object oriented API for PCRE > which can return a match object where subpattern positions and contents can > be queried via method calls, so you only pay for the parts that you do > access. Or also a literal syntax would be very very nice :-) - Markus