Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:84519
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.218.41 as permitted sender)
MIME-Version: 1.0
Sender: yohgaki@gmail.com
In-Reply-To: <54FEB910.5000608@lsces.co.uk>
References: <CAGa2bXYa5Lz0JqySVSQ+hGfCW-WxxKWvqFtWaZo=OVf+LLsV8A@mail.gmail.com>
 <5D8591E2-5AE6-4B4C-AAE0-3D15523410AC@gmail.com> <CAGa2bXa+RyQLuYe72f2m+j5c+YObfPtaOTeknMRU7p3s+96Seg@mail.gmail.com>
 <CEF2AD42-3CE1-489F-8192-D1DC3D8D8698@gmail.com> <CAGa2bXZDnuE3mKQYD+Sq2=kH=YDXuRQA3o+9wg4v81ZS+h3rLw@mail.gmail.com>
 <54F83C4D.1020206@gmail.com> <CAEZPtU6ni038E+b0ziAC1b0w=t3gsmBwMjAui4e0sXd8EgbyXQ@mail.gmail.com>
 <CAL0xaBF7u2h9A5UnVB+-z6SwDtLOVY_qL7B9UGj7w_Lecwct6A@mail.gmail.com>
 <CAGa2bXa5zER03VrMrtD9aUQ38LK9C_UWU-jbGjzEZUoxbUsSQQ@mail.gmail.com>
 <54F8BF67.6080600@gmail.com> <CAGa2bXbvZbMb5C0RnaDAVTAMK_+9x-BzidXcm9MgoaGmtWK+Zg@mail.gmail.com>
 <848D3C19-DE29-4E5F-9B23-D87D3F4A9365@gmail.com> <CAGa2bXZgx4JCv3e5a94SXwYOnLMXjYcXdMizdQ9bpqZz7oYGzQ@mail.gmail.com>
 <54FB45D6.3040803@gmail.com> <CAGa2bXYU_DRuo3T8WRuq=3Xih79BZ7vHqYOnry2AvxgVx8g0WA@mail.gmail.com>
 <54FCD063.4040300@gmail.com> <CAGa2bXYt_zHfLgKEXP+uzTH0KbeAqRmxxEAcCtsMYgyW4ptfSA@mail.gmail.com>
 <54FEB910.5000608@lsces.co.uk>
Date: Wed, 11 Mar 2015 05:44:14 +0900
Message-ID: <CAGa2bXbLVoBM+d0VVqwm8-tKaFWRE1WpMnLMaFWVHMjH4hRvDA@mail.gmail.com>
To: Lester Caine <lester@lsces.co.uk>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=e89a8fb1eabe205cc60510f539ce
Subject: Re: [PHP-DEV] Consistent function names
From: yohgaki@ohgaki.net (Yasuo Ohgaki)

--e89a8fb1eabe205cc60510f539ce
Content-Type: text/plain; charset=UTF-8

Hi Lester,

On Tue, Mar 10, 2015 at 6:27 PM, Lester Caine <lester@lsces.co.uk> wrote:

> On 10/03/15 01:59, Yasuo Ohgaki wrote:
> > The same argument applies to fresh new OO APIs. It's just a matter of
> > targeted PHP version to be supported. There are many things to be
> > considered to decide targeted PHP version other than this RFC. We have
> many
> > new features/behaviors in newer PHP versions.
>
> I still have a major problem with the whole basis of your re-naming ...
> adding the underscore at all. It was this introduction which was totally
> wrong in the first place and I would rather rename the incorrectly
> renamed functions if only to make them consistent with what is used in
> the OO 'standard'.
>
> $main->phpVersion()
> or
> phpversion()
>
> Is consistent if one maintains the case insensitive rule.
>
> Adding str_ in front of every string function where a lot are IEEE
> protected is just adding confusion. Where these map to an OO API in my book
>
> strcmp()
> $str->cmp()
>
> makes sense?
> Adding an extra $str_cmp is simply not necessary.
>
> Simply dropping the poorly formulated 'add underscore' rule which only
> currently exists on the procedural interface and tidying up the mistake
> caused by that produces a MUCH shorter list of changes and allows much
> better consistency with even the existing OO interface elements?
>
> I look at the 'tidy' gd interface and simply think 'what the ****'
>
> Yes there are some inconsistent names, but in general
> imagecolorallocate
> and
> $image->colorAllocate
>
> is more in keeping with the other graphics libraries.
>
> YES there is room to create a more consistent procedural interface, but
> my original question still applies "consistent with what rules?"


It's possible choice.
I agree that names without "_" looks more consistent.
Personally, I don't care much about having "_" or not for procedural API. My
only concern is naming consistency.

Names without "_" changes basic coding rule.
Problem is how to make a choice and how to define exceptions. e.g.
nl_langinfo()

I wonder how many of us prefer names without "_".

Regards,

--
Yasuo Ohgaki
yohgaki@ohgaki.net

--e89a8fb1eabe205cc60510f539ce--