Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:71530
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.172 as permitted sender)
MIME-Version: 1.0
Sender: yohgaki@gmail.com
In-Reply-To: <52E2CF2F.8080202@garfieldtech.com>
References: <CAGa2bXZJoyV+9qN6v8j3+vHexoqDtHR4cZkgdtdc1GpVkDaD9w@mail.gmail.com>
 <CAGa2bXY4=3UVDVdR=curS96r=pvTrxDYA0wgy+k7X46omtTPgQ@mail.gmail.com>
 <7E.A3.39789.25841E25@pb1.pair.com> <CAGAGxbb5xTCQaS7=1BPN0pWPz_Z3MqegJkaJFZfg8Eou+zELYA@mail.gmail.com>
 <12.A5.39789.B7851E25@pb1.pair.com> <52E16E01.7070401@gmail.com>
 <52E1BDB0.6050406@garfieldtech.com> <CAGa2bXYUg_YfOhbOVJpt+Hr6R5H34wb1h6dzov-sAzxz-fJtEw@mail.gmail.com>
 <52E2CF2F.8080202@garfieldtech.com>
Date: Sat, 25 Jan 2014 05:49:41 +0900
Message-ID: <CAGa2bXbmOuOAUBBA5nvUe21ZNS8RKSmDi5DaNBw-oaY471jaMQ@mail.gmail.com>
To: Larry Garfield <larry@garfieldtech.com>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=089e01493f64a0aeb204f0bd81db
Subject: Re: [PHP-DEV] Re: [PHP6] Function name consistency
From: yohgaki@ohgaki.net (Yasuo Ohgaki)

--089e01493f64a0aeb204f0bd81db
Content-Type: text/plain; charset=UTF-8

Hi Larry,

On Sat, Jan 25, 2014 at 5:38 AM, Larry Garfield <larry@garfieldtech.com>wrote:

>
>  Agreed.  Simply aliasing a bunch of functions offers no useful value, but
>>> does increase confusion.  ("Wait, do I use strcmp() or string_compare()
>>> on
>>> this project?  What version are we on again?  Oh, look, this library uses
>>> both.  Must have been different devs.  FML.")
>>>
>>> If we're going to do anything, be aggressive and far-reaching with it.
>>> Build a proper language-level OOP design for string/array manipulation.
>>>
>>> We have enough functions lying about.  Don't add more.
>>>
>>
>>
>> We should be careful choosing names. I agree.
>> However, not adding more function names is simply impossible.
>> For example, I'm about to add new session function named
>>
>> string session_create_id([string $prefix])
>>
>> for user save handlers, so that user could generate secure ID
>> easily. It's a straight name for session ID creation and there
>> might be users using this name.
>>
>> Not adding any new names means not adding any new features
>> nor cleanups.
>>
>> Regards,
>>
>
> I don't mean "never add a function again".  I mean adding functions for no
> particular value other than having more of them helps nothing, and arguably
> makes the situation worse.  Where possible, we shouldn't be adding
> yet-another-utility-function but looking to how to build more complete and
> functional language capabilities and standard libraries, rather than
> piecemeal addition of functions one RFC at a time.
>
> For your example, for instance, session handling is as of PHP 5.4 an
> object.  That's the cleaner way to handle it than a bunch of functions.
>  Can that function be better integrated into an API rather than just added
> to a long list of tools?  I don't know; maybe.  But we should be asking
> those questions, not saying "how many more ways to type strcmp() can we
> introduce to confuse people."


I think we have different objective.

 - Better PHP for *future* users.
vs
 - Better PHP for *current* users.

Both objectives are important, IMHO.
My intention is to make/keep PHP attractive language to learn.

We have namespace, so name collision is not much issue
now a days, isn't it? I know there are many apps w/o namespace,
though. There is a way to work round at least.

Regards,

--
Yasuo Ohgaki
yohgaki@ohgaki.net

--089e01493f64a0aeb204f0bd81db--