Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:104770 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 85145 invoked from network); 16 Mar 2019 11:56:29 -0000 Received: from unknown (HELO vie01a-dmta-pe05-1.mx.upcmail.net) (84.116.36.11) by pb1.pair.com with SMTP; 16 Mar 2019 11:56:29 -0000 Received: from [172.31.216.235] (helo=vie01a-pemc-psmtp-pe12.mail.upcmail.net) by vie01a-dmta-pe05.mx.upcmail.net with esmtp (Exim 4.88) (envelope-from ) id 1h54yN-0003ls-1p for internals@lists.php.net; Sat, 16 Mar 2019 09:47:19 +0100 Received: from mail02.home ([213.47.8.56]) by vie01a-pemc-psmtp-pe12.mail.upcmail.net with ESMTP id 54xPhM3K3xLwq54xPhV0mD; Sat, 16 Mar 2019 09:46:19 +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=pav7nIVWqzT6zyY-TJgA: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 1h54xO-0005mX-CA for internals@lists.php.net; Sat, 16 Mar 2019 09:46:18 +0100 To: internals@lists.php.net References: Message-ID: <051bac84-2600-ba52-efad-ef0b3af27291@fischer.name> Date: Sat, 16 Mar 2019 09:49:22 +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: 8bit 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 14.03.19 20:33, C. Scott Ananian wrote: > ps. more ambitious would be to introduce a new "substring" type, which > would share the allocation of a parent string with its own offset and > length fields. That would probably be as invasive as the ZVAL_INTERNED_STR > type, though -- a much much bigger project. [...] 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: MS4wfFi/XWAyEnj//G9hQjM4ZrfrFQCB2kIwJoUGC7ADYIAo/3bXFMeHIh4o8slJRQ2bdTNS85YsqaMsgHVYjqXs27Lpg5CfY8cALhnf4LzKYvl4DyhcbHg8 eRXtGa3uJze1rZeTB5GgWX3p/iPpjnEu5ZH4qhhVV9rhSm37KVBllJfg Subject: Re: [PHP-DEV] Offset-only results from preg_match From: markus@fischer.name (Markus Fischer) On 14.03.19 20:33, C. Scott Ananian wrote: > ps. more ambitious would be to introduce a new "substring" type, which > would share the allocation of a parent string with its own offset and > length fields. That would probably be as invasive as the ZVAL_INTERNED_STR > type, though -- a much much bigger project. That feature would be incredible to have. Erlang/Elixir use these concept and it's incredible what they can do with this. However, the data types there are also immutable so it's whole other league… - Markus