Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:115354
MIME-Version: 1.0
References: <CAPVMwwt=7ojR-yH8k2L0+wjMrpJJooVYsTVMDqjd79q7fUHcNg@mail.gmail.com>
In-Reply-To: <CAPVMwwt=7ojR-yH8k2L0+wjMrpJJooVYsTVMDqjd79q7fUHcNg@mail.gmail.com>
Date: Wed, 7 Jul 2021 21:38:09 +0200
Message-ID: <CAFPFaMLxFDGp6ksxkLePQr5WL5Jw0ci=pnF9VA+0qHhh7x1E5Q@mail.gmail.com>
To: Dmitry Stogov <dmitrystogov@gmail.com>
Cc: PHP Internals <internals@lists.php.net>, Nikita Popov <nikita.ppv@gmail.com>, 
	Alexandr Lisachenko <lisachenko.it@gmail.com>
Content-Type: multipart/alternative; boundary="00000000000052820505c68dae55"
Subject: Re: [PHP-DEV] FFI Type Reflection API
From: george.banyard@gmail.com ("G. P. B.")

--00000000000052820505c68dae55
Content-Type: text/plain; charset="UTF-8"

On Wed, 7 Jul 2021 at 10:31, Dmitry Stogov <dmitrystogov@gmail.com> wrote:

> Hi,
>
> Last week, at a PHP conference, we discussed some missing parts of ext/ffi
> with one of the most extrimal FFI user - Alexandr Lisachenko. One of the
> things he is missing is a FFI Type Reflection API. Actually, this is a
> simple and self-contained feature, that implementation took me a couple of
> hours.
>
> https://github.com/php/php-src/pull/7217
>
> This doesn't touch any existing code in ext/ffi, just add the API that is
> better visible through stub:
>
> https://github.com/php/php-src/pull/7217/files#diff-3651c407d02a2a152d9aba6e484f6ae7f4c2c85fa2992274d76c0e18364c7e6fL75-R96
>
> Unfortunately, PHP-8.1 is closed for new RFC, so we can merge this as a
> self-contained feature, or wait for the next version. I ask to merge this
> into PHP-8.1, but won't do this, in case of any objections.
>
> Thanks. Dmitry.
>

Ideally the array/struct/function CTypes would be subclasses,
but if due to time constraints going down this route is impossible,
it is still better to have this information available then not at all.

So +0.5 on principle (seeing that there already is a naming bikeshed I'm
not going to chime in on this aspect).

Best regards,

George P. Banyard

--00000000000052820505c68dae55--