Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:103587
To: Marco Pivetta <ocramius@gmail.com>, Dmitry Stogov <dmitry@zend.com>
Cc: PHP Internals List <internals@lists.php.net>
References: <BY1PR02MB126022AD4151506F6486D6A7BFA90@BY1PR02MB1260.namprd02.prod.outlook.com>
 <CADyq6s+GZ4qyUsYDtHX2qSnP+jJFw9UQxtVq2zLfBUa2OVxbXA@mail.gmail.com>
Message-ID: <6cd879da-b622-3265-e9ca-771badd228e0@gmx.de>
Date: Tue, 11 Dec 2018 19:33:23 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101
 Thunderbird/60.3.3
MIME-Version: 1.0
In-Reply-To: <CADyq6s+GZ4qyUsYDtHX2qSnP+jJFw9UQxtVq2zLfBUa2OVxbXA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: de-DE
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC] FFI - Foreign Function Interface
From: cmbecker69@gmx.de ("Christoph M. Becker")

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