Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:65218
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.172 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAJW__o1MbvBA9KJ-0zpYDA9Wx3Rnekz7FW8JMYyQ+G=EUFghGA@mail.gmail.com>
References: <CAGsPR66hpGfvtZQw9A_-Jc-jqEdhWkbq8km1GYZ0K9Ycx9Vn1w@mail.gmail.com>
 <CAJW__o1MbvBA9KJ-0zpYDA9Wx3Rnekz7FW8JMYyQ+G=EUFghGA@mail.gmail.com>
Date: Sat, 26 Jan 2013 19:34:46 +0200
Message-ID: <CAA9esyTAh+UxRvHbgb0P2nmckck+9VWNRYy+Sefj0bhBAQ6EfQ@mail.gmail.com>
To: Kalle Sommer Nielsen <kalle@php.net>
Cc: =?UTF-8?Q?Damian_Tylczy=C5=84ski?= <turneliusz@gmail.com>, 
	internals@lists.php.net
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] I think that "Function naming inconsistency" bug
 deservers more attention
From: florinpatan@gmail.com (Florin Razvan Patan)

Hi,

Everyone here forgets that there's a little certification
run by some guys named Zend  that factor in some of
these things as well.

That's the point of not having consistency? Checking
if some have better memory that others?

Also, I suppose that everyone can afford to look up
things on the PHP manual when doing debugging on
some crashed remote service via CLI only access.

Now, on a nicer tone.

Consistency across function name/parameters would
help out both new people that learn the language as
well as leave out one point when compared to the other
languages.

Sure, there's no point in changing things just for the
sake of it but I don't get it why this couldn't be a
viable option for PHP 6 for example, which is a major
release.

It would definitely help out new users and get some
bonus points while doing so in order to close the mouth
of those arguing that PHP is so inconsistent in naming
things.

Phil Sturgeon had a nice idea on his blog,
http://philsturgeon.co.uk/blog/2013/01/php-6-pissing-in-the-wind
which I think could very well apply to PHP and maybe
something like this could be done by someone with
less C/PHP internals knowledge that some other
features. If that's the case and all we need is someone
to do the changes, then I could level up my C
knowledge and help out if no one else is willing to do
it.

I'd dislike for it to be rejected with reasons like:
- but it doesn't bring anything new;
- it doesn't help us with anything;
- it doesn't solve real problems;
- the current functions reflect the underlying functions
used. I've been a PHP user (developer) for a couple  of
years now and I really don't care what's the parameter
order for the functions that PHP use to help me out
getting my job done;
- perfection ain't good.


Best regards.
----
Florin Patan
https://github.com/dlsniper




On Sat, Jan 26, 2013 at 7:13 PM, Kalle Sommer Nielsen <kalle@php.net> wrote=
:
> Hi
>
> 2013/1/25 Damian Tylczy=C5=84ski <turneliusz@gmail.com>:
>> I've seen discussion on reddit
>> http://www.reddit.com/r/PHP/comments/174qng/lets_make_phps_function_name=
s_consistent/
>
> There is one really clean solution to this "problem" for the
> consistency Guys that tend to complain about PHP endlessly; write the
> aliases in PHP that can be included, which can be considered just like
> using one of the frameworks thats filled with functions, it can be
> written quite fast and you can even use auto_prepend_file to include
> it in all scripts.
>
> As said in countless mails above, there is no gain for breaking BC due
> to "perfection".
>
> --
> regards,
>
> Kalle Sommer Nielsen
> kalle@php.net
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>