Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:103637
To: Derick Rethans <derick@php.net>, internals@lists.php.net
References: <07B8181B-DA10-49AD-A4A3-C5AE40684312@php.net>
Message-ID: <eb94cbc4-b0fb-6eb7-44ff-cd584cb5a479@gmail.com>
Date: Tue, 25 Dec 2018 13:17:58 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101
 Thunderbird/60.3.3
MIME-Version: 1.0
In-Reply-To: <07B8181B-DA10-49AD-A4A3-C5AE40684312@php.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC] [VOTE] FFI - Foreign Function Interface
From: jgmdev@gmail.com (Jefferson Gonzalez)

On 12/25/18 12:20 PM, Derick Rethans wrote:
> There is no need to go from new extension with a new unproven API to directly into core as first try. It's much better to try things out in for example PECL and then to promote it to a core extension when all the kinks are worked out.
> 

True, but in this case Dmitry clarified that the Api is mostly a mirror 
of the Python or Lua FFI implementations, and both have been already 
proven to work and satisfy most needs, so basically the wheel isn't been 
reinvented here, it could be said that this is an adaptation of the 
wheel which structure is already well known.

By the way, Merry Christmas to all!