Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:103584
MIME-Version: 1.0
References: <BY1PR02MB126022AD4151506F6486D6A7BFA90@BY1PR02MB1260.namprd02.prod.outlook.com>
 <CADyq6s+GZ4qyUsYDtHX2qSnP+jJFw9UQxtVq2zLfBUa2OVxbXA@mail.gmail.com> <BY1PR02MB1260BD6551B3F3D0B43BC9B0BFA60@BY1PR02MB1260.namprd02.prod.outlook.com>
In-Reply-To: <BY1PR02MB1260BD6551B3F3D0B43BC9B0BFA60@BY1PR02MB1260.namprd02.prod.outlook.com>
Date: Tue, 11 Dec 2018 16:42:25 +0100
Message-ID: <CADyq6s+m3=BxCkc2xrPvCcvMnj9kG+L82B=_5fBH-5gThBR6uw@mail.gmail.com>
To: Dmitry Stogov <dmitry@zend.com>
Cc: PHP Internals List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000005bee3a057cc0eedc"
Subject: Re: [PHP-DEV] [RFC] FFI - Foreign Function Interface
From: ocramius@gmail.com (Marco Pivetta)

--0000000000005bee3a057cc0eedc
Content-Type: text/plain; charset="UTF-8"

 > People who don't know what FFI is, don't need it.

I think this is a very dangerous way of designing, writing and documenting
software.

I appreciate your efforts in pushing this forward, but please reconsider
when approaching the naming problematic, because this point of view is
extremely flawed.

Marco Pivetta

http://twitter.com/Ocramius

http://ocramius.github.com/


On Tue, Dec 11, 2018 at 4:37 PM Dmitry Stogov <dmitry@zend.com> wrote:

> Hi Marco,
>
>
> Some API and naming issues may be changed, e.g. FFI::array_type() was
> renamed to FFI::arrayType().
>
> Changing FFI into ForeignFunctionInterface looks, like an overhead.
> People who don't know what FFI is, don't need it.
>
>
> I surprised, there are no any problem reports...
>
> It seems, like few people on @internals tried it.
>
>
> Thanks. Dmitry.
>
>
>
>
> ------------------------------
> *From:* Marco Pivetta <ocramius@gmail.com>
> *Sent:* Thursday, December 6, 2018 7:26:57 PM
> *To:* Dmitry Stogov
> *Cc:* PHP Internals List
> *Subject:* Re: [PHP-DEV] [RFC] FFI - Foreign Function Interface
>
> Looks very interesting, especially for simplifying the landscape of
> extensions.
>
> Still, the amount of abbreviations and naming issues is quite huge: needs
> a lot of care on that end, IMO. Even just the name of the type (`FFI`) can
> simply be expanded to `ForeignFunctionInterface`.
>
> Just my 2 cents.
>
> Marco Pivetta
>
> http://twitter.com/Ocramius
>
> http://ocramius.github.com/
>
>
> On Thu, Dec 6, 2018 at 4:54 PM Dmitry Stogov <dmitry@zend.com> wrote:
>
> Hi Internals,
>
>
> I would like to start discussion of FFI RFC https://wiki.php.net/rfc/ffi
>
>
> This extension allows calling C function and accessing C data structures
> in pure PHP.
>
> In conjunction with preloading it gives a  possibility to write PHP
> extension in PHP itself.
>
> The extension was tested on attempt to build TensorFlow PHP binding.
>
>
> Thanks. Dmitry.
>
>

--0000000000005bee3a057cc0eedc--