Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:103588
MIME-Version: 1.0
References: <BY1PR02MB126022AD4151506F6486D6A7BFA90@BY1PR02MB1260.namprd02.prod.outlook.com>
 <CADyq6s+GZ4qyUsYDtHX2qSnP+jJFw9UQxtVq2zLfBUa2OVxbXA@mail.gmail.com> <6cd879da-b622-3265-e9ca-771badd228e0@gmx.de>
In-Reply-To: <6cd879da-b622-3265-e9ca-771badd228e0@gmx.de>
Date: Tue, 11 Dec 2018 13:21:06 -0700
Message-ID: <CAFMT4Nr5Qzyvu13QjoPB01RRgLGCS7QZ8GgDgnx2txvjsU7rGw@mail.gmail.com>
To: Christoph Becker <cmbecker69@gmx.de>
Cc: Marco Pivetta <ocramius@gmail.com>, Dmitry Stogov <dmitry@zend.com>, 
	internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000003fb7fa057cc4d371"
Subject: Re: [PHP-DEV] [RFC] FFI - Foreign Function Interface
From: levim@php.net (Levi Morrison)

--0000000000003fb7fa057cc4d371
Content-Type: text/plain; charset="UTF-8"

On Tue, Dec 11, 2018 at 11:33 AM Christoph M. Becker <cmbecker69@gmx.de>
wrote:

> On 06.12.2018 at 17:26, Marco Pivetta wrote:
>
> > 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`.
>
> By the same reasoning, http_response_code() is a bad name, and should be
> changed to hyper_text_transfer_protocol_response_code().  Same for
> parse_url(), which should better be named
> parse_uniform_resource_locator(). ;)
>
> Don't get me wrong, I'm all for having self-explaining identifiers, but
> if within a given domain an abbreviation is *very* common, it makes not
> much sense to spell it out.  And FFI is very common when interfacing to
> C from a scripting language.
>
> --
> Christoph M. Becker
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php


My only nit on naming is that "FFI" needs to specify in some way *which*
FFI. Although an FFI with C is very common it is not the only one that
exists. Naming this "CFFI" or such would solve this.

--0000000000003fb7fa057cc4d371--