Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:108703 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 35922 invoked from network); 20 Feb 2020 18:31:14 -0000 Received: from unknown (HELO localhost.localdomain) (76.75.200.58) by pb1.pair.com with SMTP; 20 Feb 2020 18:31:14 -0000 To: internals@lists.php.net References: Date: Thu, 20 Feb 2020 16:47:25 +0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.4.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit X-Posted-By: 94.8.9.87 Subject: Re: [RFC] Explicit call-site pass-by-reference (again) From: marandall@php.net (Mark Randall) Message-ID: On 20/02/2020 14:13, Nikita Popov wrote: > The RFC proposes to allow using a "&" marker at the call-site (in addition > to the declaration-site) when by-reference passing is used. It's a solid +1 from me I do think this is somewhere else that an "official" upgrade / migration tool would be rather well-received, an easy mechanism to scan a file / directory for standard extension functions with known reference args and re-write them appropriately. -- Mark Randall marandall@php.net