Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:65192
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.83.43 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 20:24:33 +0100
Message-ID: <CAGsPR64L+8H+JfeqhhH1BWZFPYoDYus4rW0UdKrdwJGef20=SQ@mail.gmail.com>
To: Rasmus Lerdorf <rasmus@lerdorf.com>
Cc: internals@lists.php.net, Seva Lapsha <seva.lapsha@gmail.com>, 
	Stas Malyshev <smalyshev@sugarcrm.com>
Content-Type: multipart/alternative; boundary=047d7b5dbec29c864204d421e016
Subject: Re: [PHP-DEV] I think that "Function naming inconsistency" bug
 deservers more attention
From: turneliusz@gmail.com (=?ISO-8859-2?Q?Damian_Tylczy=F1ski?=)

--047d7b5dbec29c864204d421e016
Content-Type: text/plain; charset=ISO-8859-2
Content-Transfer-Encoding: quoted-printable

Yes, it's extremely useful, especially because most of the php developers
are developing under Linux and most of them are coming from C and many
other languages. Give ma a break... Second thing, we're afraid of throwing
deprecated errors. Let's see the case. On production machines there are
errors hidden from the users (display errors: none or just strict, notice,
deprecated types hidden), experienced developers when they will not like
them during development will disable them or migrate their code, new
developers will just learn new API. Where is the problem? I'm not talking
about removing some functions but just deprecating them to to get some time
and simply to be ready to improve the PHP as a language in the future when
time will come.
25 sty 2013 20:04, "Rasmus Lerdorf" <rasmus@lerdorf.com> napisa=B3(a):

> 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 bundle=
d
> > 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
>
>

--047d7b5dbec29c864204d421e016--