Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:84207
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain fischer.name from 62.179.121.34 cause and error)
Message-ID: <54F4F3FC.6060501@fischer.name>
Date: Tue, 03 Mar 2015 00:36:28 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: internals@lists.php.net
References: <CAGa2bXYa5Lz0JqySVSQ+hGfCW-WxxKWvqFtWaZo=OVf+LLsV8A@mail.gmail.com> <CAEZPtU41xa1yrLPYn_VHx-axOmuM4_KAa00zwPRhpm5ZLSbQ+Q@mail.gmail.com> <CAGa2bXZD1MJojzFu8FwmGKH7gZxpqP7bNUusgQ3YzEpBduCs_g@mail.gmail.com> <CAEZPtU6=KY2tzRE8yw6kEdh4SrVJ3uG81XX5yuu0E_63G1HN6g@mail.gmail.com> <54F4E29D.7080501@garfieldtech.com> <CAGa2bXbph51CUHr_G87FL65hSDfLSDHo14Bnke-vaLu7SmH=ZQ@mail.gmail.com> <54F4E93C.80206@gmail.com> <54F4EBEC.2090702@garfieldtech.com> <CAGa2bXaQ0SgLWdv7WCoo_qyOQH=t2Vi_bwpk7qXZDEUk+7S7ew@mail.gmail.com>
In-Reply-To: <CAGa2bXaQ0SgLWdv7WCoo_qyOQH=t2Vi_bwpk7qXZDEUk+7S7ew@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Spam_score: -2.9
X-Spam_score_int: -28
X-Spam_bar: --
X-Spam_report: Spam detection software, running on the system "scanner01.home", has
 identified this incoming email as possible spam.  The original message
 has been attached to this so you can view it (if it isn't spam) or label
 similar future email.  If you have any questions, see
 the administrator of that system for details.
 
 Content preview:  On 03.03.15 00:10, Yasuo Ohgaki wrote: > I would love to have
    new & clean APIs. > > Please think my proposal as legacy API cleanups. Many
    of candidates will > remain > without CORDING_STANDARSDS confirmed names
   almost forever. This is what > I would like to improve. If you don't care
   about legacy stuff cleanups, > please don't > care. The cleanups will not
   hurt anything, almost. [...] 
 
 Content analysis details:   (-2.9 points, 5.0 required)
 
  pts rule name              description
 ---- ---------------------- --------------------------------------------------
 -1.0 ALL_TRUSTED            Passed through trusted hosts only via SMTP
 -1.9 BAYES_00               BODY: Bayes spam probability is 0 to 1%
                             [score: 0.0000]
Subject: Re: [PHP-DEV] Consistent function names
From: markus@fischer.name (Markus Fischer)

On 03.03.15 00:10, Yasuo Ohgaki wrote:
> I would love to have new & clean APIs.
> 
> Please think my proposal as legacy API cleanups. Many of candidates will
> remain
> without CORDING_STANDARSDS confirmed names almost forever. This is what
> I would like to improve. If you don't care about legacy stuff cleanups,
> please don't
> care. The cleanups will not hurt anything, almost.

No ill intentions here, but adding the aliases and, as you propose,
literally adding *hundreds* of aliases is actually a mess to me.

What you call "new & clean" is as a shield for effectively introducing
duplicates. You do not clean up anything that way. You leave a even
bigger mess behind. By going for your honorable goal of correcting
things I think you got lost in the woods.

IMHO the only forward is to make sure new/future additions to the
language adhere to the coding standard or use a smart way (i.e. the
scalar addition).

- Markus