Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:106482 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 3740 invoked from network); 9 Aug 2019 14:26:28 -0000 Received: from unknown (HELO localhost.localdomain) (76.75.200.58) by pb1.pair.com with SMTP; 9 Aug 2019 14:26:28 -0000 To: internals@lists.php.net References: <5d4ca16b.1c69fb81.bcb4a.9e51SMTPIN_ADDED_MISSING@mx.google.com> <5d4cb5da.1c69fb81.5608d.7c4bSMTPIN_ADDED_MISSING@mx.google.com> Date: Fri, 9 Aug 2019 12:53:51 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 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.4.34.143 Subject: Re: [PHP-DEV] Re: Bringing Peace to the Galaxy From: markyr@gmail.com (Mark Randall) Message-ID: On 09/08/2019 08:15, Zeev Suraski wrote: > I'm unable to follow that part either. Would appreciate some further > elaboration to make it clearer what you have in mind in these three > paragraphs... My read of what Nikita was suggesting was some kind of per-file or per-package versioning system that would operate at compile time to add new features at compiler / parser level, and presumably keep them running on the same VM. What I am less sure about is how it would handle BC between versions of the API, the example I gave was reflection and union types. Perhaps I mistook his intention. Mark Randall