Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:101224
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.179 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <N1M-N3MmY7pQYF@Safe-mail.net>
References: <N1M-N3MmY7pQYF@Safe-mail.net>
Date: Sat, 2 Dec 2017 20:41:36 -0500
Message-ID: <CAL+t6cEgGzdt+yV7+whu-JJo7rE4Gk9idHtupWUL-J9MU7H9iQ@mail.gmail.com>
To: Alexei Gerasimov <enclaved@safe-mail.net>
Cc: Andreas Hennings <andreas@dqxtech.net>, Niklas Keller <me@kelunik.com>, 
	"Christoph M. Becker" <cmbecker69@gmx.de>, PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="001a113e5180d11bbf055f65b372"
Subject: Re: [PHP-DEV] C++-like function-try-block proposal
From: theanomaly.is@gmail.com (Sherif Ramadan)

--001a113e5180d11bbf055f65b372
Content-Type: text/plain; charset="UTF-8"

On Sat, Dec 2, 2017 at 3:44 PM, Alexei Gerasimov <enclaved@safe-mail.net>
wrote:

>
>
> > Let's not forget PHP 5 has been around for over a decade before PHP 7
> even
> > showed up. There are still a lot of old code basis that've been running
> in
> > PHP 5 for years. And for large code basis with deep rooted legacy, it is
> no
> > short order to make the leap. Change for the sake of change won't help
> that.
>
> I lost it here. I'm proposing a backward-compatible change, so why speak of
> legacy and existing codebases?
>


There's no argument that the change is not forward-compatible. I'm merely
pointing out the burden of adding new language features. This is not to
deter from adding them, but to caution against excess. There is a cost to
learning a new language feature, updating its documentation, considering
its trade offs in software design, etc... Part of this cost is shared
between those who maintain PHP and those who use PHP.

My statements here are intended to be cautionary, not dissuasive.

--001a113e5180d11bbf055f65b372--