Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:101223
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain Safe-mail.net designates 212.29.227.83 as permitted sender)
DomainKey-Status: good
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
	s=N1-0105; d=Safe-mail.net;
	b=xyhDSGQ5UUOC/MHaP8V9tcACFvxDfe0XnCoIif1SfmyLcax0Xn4TT44AtPT5WTcK
	3dzG7Q2np6/VLNY+AdoUzfReZMdihLaF/jtKBD3odrAAm12wF9pC9uWaLyQzQwLN
	eZ0qIFWQiJdzqQY5TeX4ITnpITGqz8aPjqqPnU9ENZE=;
Date: Sat, 2 Dec 2017 23:44:50 +0300
To: theanomaly.is@gmail.com
CC: andreas@dqxtech.net, me@kelunik.com, cmbecker69@gmx.de, internals@lists.php.net
Message-ID: <N1M-N3MmY7pQYF@Safe-mail.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] C++-like function-try-block proposal
From: enclaved@Safe-mail.net ("Alexei Gerasimov")

> I'd like to see an RFC that demonstrates a stronger use case than "avoiding
> one level of indentation and <just cause we can>", however.

Sure, as soon as I am able to register and write on wiki.php.net.

> 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?