Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:101170
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=HSx3NwFKpkSIYqhRbZGEPKFApzn2RV1C204ufGBCJlDDD3izUu2r9WNR2cxaf0ED
	CGvWV2dnHZNgOnZQc4H0dVSZp91F/QkDI7OdbbDoVqBqX36QzO1q4KVdn05XW6RP
	jB09uGbtjnIUKdvXhM/5PddiNa7eO2v6HqN4dlSCrmM=;
Date: Mon, 27 Nov 2017 21:41:19 +0300
To: pollita@php.net
CC: internals@lists.php.net
Message-ID: <N1M-lWkkMNmzxO@Safe-mail.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] C++-like function-try-block proposal
From: enclaved@Safe-mail.net ("Alexei Gerasimov")

> > Since PHP is partially influenced by C++, I believe this syntax would be
> > a meaningful step in making PHP a little bit more intuitively compatible
> > with C++ practices, which may prove useful for people who come to PHP from
> > the C++ world (such as myself.)  The expected benefit is PHP becomes yet
> > more familiar and comfortable for C++ programmers.
> >
> I'm not sure this statement is entirely accurate.  PHP's fundamental
> inspirations come from perl and C.  It's OOP layer was inspired in
> part from C++, but also from Java.

Oh, I didn't mean to single C++ out, hence "partially". When I started with =
PHP OOP not too long ago, I kinda expected that function-try-block construct =
to work, for no real reason other than a hunch, and it didn't. So after taking =
a look at the parser, I figured it wouldn't be a big deal to add it just as =
syntactic sugar (Nikita pointed it out correctly that in C++ it was introduced =
for the purpose of wrapping around initalizer lists.) After all it'd cost us =
just one additional level of yacc grammar, i.e. nothing to worry about performance-wise.

I could try to come up with a better and more realistic use case example for =
it if I am ever allowed to make an actual RFC out of it. But still, perhaps =
my best argument is that it is very cheap to implement, and may potentially =
make code look neater.

-Alexei