Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:101220
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.181 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAH0Uv3HABGzV4Vta-mjmnx4cUX8K0rDFBj_uWzFH83mNG+f=3Q@mail.gmail.com>
References: <N1M-adRkRLsZIQ@Safe-mail.net> <CAH0Uv3HABGzV4Vta-mjmnx4cUX8K0rDFBj_uWzFH83mNG+f=3Q@mail.gmail.com>
Date: Sat, 2 Dec 2017 15:02:32 -0500
Message-ID: <CAL+t6cHmfSd8DYG+0=wwCKhJV4i6pWXOnJ=yv6vHYQv27UG4dQ@mail.gmail.com>
To: Andreas Hennings <andreas@dqxtech.net>
Cc: Alexei Gerasimov <enclaved@safe-mail.net>, Niklas Keller <me@kelunik.com>, 
	"Christoph M. Becker" <cmbecker69@gmx.de>, PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="001a113e51803857bc055f60f777"
Subject: Re: [PHP-DEV] C++-like function-try-block proposal
From: theanomaly.is@gmail.com (Sherif Ramadan)

--001a113e51803857bc055f60f777
Content-Type: text/plain; charset="UTF-8"

I think we get this "I want to make PHP more like <language X>" thing more
often than any other language change proposals. I'm not strictly opposed to
the idea of borrowing from other languages. Though when the thesis
statement is almost exclusively about making PHP feel more like <language
X> than anything else I'd rather not entertain the idea further.

I agree with Nikita that this feature in C++ adds no intrinsic value to
PHP. I'm never overly excited about purely syntactic sugar changes in PHP.
We've already changed so much of the language in PHP 7 that I'm finding
some people struggling with keeping up with PHP 5 - 7 migration paths (and
I'm speaking from first hand experience having to deal with one myself at
work).

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. Kind of erring
on the side of +0 with Sara here.

On Sat, Dec 2, 2017 at 1:13 PM, Andreas Hennings <andreas@dqxtech.net>
wrote:

> So to summarize, this feature would save us brackets and one indentation
> level.
> Saving an indentation level can be quite useful to reduce a git commit
> footprint.
>
> On the other hand, it might confuse some people. It would blur the concept
> of a function body scope, and thus the mental model of how the language
> works.
> E.g. are local variables and parameters shared between the try {} and the
> catch {} block?
>
> It would also mean that userland PHP parsers and IDEs need to support the
> syntax.
>
> So personally I am undecided or skeptical. It does feel alien to me.
> Usually if I want to avoid the extra indentation, I will put the try {}
> part into a separate function.
> But this is just me.
>
>
> On 2 December 2017 at 14:27, Alexei Gerasimov <enclaved@safe-mail.net>
> wrote:
>
> > > > I did (using this e-mail address), and got the message: "The user has
> > been created and the password was sent by email." However, I did not
> > receive any e-mail with the password.
> > >
> > > Sorry for the trouble, seems like nobody tested the sign up process
> > after the server migration yet. It seems like the e-mail sender
> > configuration is missing.
> > >
> > >
> > > Unfortunately, I don't know the right config, so I can't simply fix it,
> > but I've sent a message to Hannes, he probably knows.
> >
> > Any update? The reset password feature of wiki.php.net doesn't work
> > either, I receive no e-mail.
> >
> > --
> > PHP Internals - PHP Runtime Development Mailing List
> > To unsubscribe, visit: http://www.php.net/unsub.php
> >
> >
>

--001a113e51803857bc055f60f777--