On Sat, Dec 2, 2017 at 3:44 PM, Alexei Gerasimov
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 i
> I'd like to see an RFC that demonstrates a stronger use case than "avoiding
> one level of indentation and ", 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 lo
On Sat, Dec 2, 2017 at 3:08 PM, Alexei Gerasimov
wrote:
>
> I don't think we should be worried about changes _other_ projects would
> have to make to cope up with language evolution lest it becomes an
> (unnecessary and surrogate) obstacle. My vision is that if some
> company/group produces an ID
> 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?
PHP documentation stresses it that the scope is always the entire function,
i.e. it isn't li
I think we get this "I want to make PHP more like " 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 than anything else I'd rathe
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 th
> > 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. I