Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:65200
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.173 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <5102D753.5040900@lerdorf.com>
References: <CAGsPR66hpGfvtZQw9A_-Jc-jqEdhWkbq8km1GYZ0K9Ycx9Vn1w@mail.gmail.com>
	<5102D1DB.9060305@sugarcrm.com>
	<CAOtCo3qM5oQu4wpn_zhVpyPFDVemxKfBOmB2Qp7dKhUyoot2bw@mail.gmail.com>
	<5102D753.5040900@lerdorf.com>
Date: Fri, 25 Jan 2013 19:59:05 -0800
Message-ID: <CAFWS2+HRCz2RfEhFN59wohnXQLJErY64KzSQjSf79weoAAOLyg@mail.gmail.com>
To: Rasmus Lerdorf <rasmus@lerdorf.com>
Cc: Seva Lapsha <seva.lapsha@gmail.com>, Stas Malyshev <smalyshev@sugarcrm.com>, 
	=?ISO-8859-2?Q?Damian_Tylczy=F1ski?= <turneliusz@gmail.com>, 
	"internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=e89a8f22bec1acafe404d42910d3
Subject: Re: [PHP-DEV] I think that "Function naming inconsistency" bug
 deservers more attention
From: ronabop@gmail.com (Ronald Chmara)

--e89a8f22bec1acafe404d42910d3
Content-Type: text/plain; charset=ISO-8859-1

Here I am, ten years later, and the same issue is being rehashed just as it
was when it was brought up ten years ago.

Over those ten years, things have slowly gotten better, but the underlying
issue remains the same. PHP is glue. PHP has not taken the path of
re-naming everything to conform to a new "PHP standard", other than
underscores, and attempts at function prefixes.

Sure, we could start adding aliases like libc_strlen(), and maybe that's
worth a thought, but its adding another layer of complexity, to achieve
simplicity.


On Fri, Jan 25, 2013 at 11:04 AM, Rasmus Lerdorf <rasmus@lerdorf.com> wrote:

> On 01/25/2013 10:55 AM, Seva Lapsha wrote:
> > Well, how about renaming the functions, create aliases for BC and throw
> > E_DEPRECATED or E_STRICT on their usage? And write a PEAR script bundled
> > with the distribution to migrate to the new convention?
>
> Throwing warnings on perfectly working code is really a bad idea. It
> annoys users, slows down their code, and doesn't add any value at all to
> them.
>
> It should also be noted that many of the function names that people
> don't think are consistent are actually quite consistent when you
> consider that PHP is just a thin wrapper on top of underlying libraries.
> Functions from libc like tempnam() and strlen() are perfectly fine. The
> fact that you can go to your Linux command line and type: "man tempnam"
> to get a good idea of what is happening behind the scenes of the PHP
> function of the same name is a good thing.
>
> -Rasmus
>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--e89a8f22bec1acafe404d42910d3--