Live data from Hacker News

Upcoming changes in PHP 7.1

dotdev.co

1–10 of 137 posts

Re: Upcoming changes in PHP 7.1

#3
Off topic, but curious - Is there any discussion on whether there will be a support for a good concurrent programming in PHP in the future? (e.g. channels in Go & Elixir) - of course, you might say "you're using the wrong tool.."

Re: Upcoming changes in PHP 7.1

#4

Off topic, but curious - Is there any discussion on whether there will be a support for a good concurrent programming in PHP in the future? (e.g. channels in Go & Elixir) - of course, you might say "you're using the wrong tool.."

React has been around for a while - http://reactphp.org/

Re: Upcoming changes in PHP 7.1

#5

Off topic, but curious - Is there any discussion on whether there will be a support for a good concurrent programming in PHP in the future? (e.g. channels in Go & Elixir) - of course, you might say "you're using the wrong tool.."

I don't know if you can classify it as "good" concurrent programming but there's this https://github.com/krakjoe/pthreads

EDIT "pthreads v3 is restricted to operating in CLI only" - from the project page.

Re: Upcoming changes in PHP 7.1

#6
post #2

This is just an excerpt from https://dotdev.co/upcoming-changes-in-php-7-1-76ebea53b820#....

My favorite feature is definitely the square bracket destructuring syntax. This is great for bringing tuple-esque operations to the language.

Re: Upcoming changes in PHP 7.1

#8

Off topic, but curious - Is there any discussion on whether there will be a support for a good concurrent programming in PHP in the future? (e.g. channels in Go & Elixir) - of course, you might say "you're using the wrong tool.."

Using Redux with React or Vuejs is a good way to go!

Re: Upcoming changes in PHP 7.1

#9
... Note the syntax isn’t the usual double pipe || operator that we associate with or, rather a single pipe | character ...

... PHP 7.1 introduces visibility modifiers to constants ...

... With PHP 7.1 it is now possible to specify that a function has a void return type, i.e. it performs an action but does not return anything ...

... Example four contains numeric values, so everything else is stripped out, and the sum of those are used to calculate the total of 10. But it would still be nice to see a warning, as this may not be intended behaviour ...

Good to see PHP continues to introduce new inconsistencies while striving to break existing code by fixing old ones. Best of both worlds!

edit: OK this was uncharitable and technically some of them are not inconsistencies, just things I thought were weird. I know PHP is widely used and considered useful and will stay with us forever. But I found those snippets interesting.

Re: Upcoming changes in PHP 7.1

#10
post #6
post #2

This is just an excerpt from https://dotdev.co/upcoming-changes-in-php-7-1-76ebea53b820#....

My favorite feature is definitely the square bracket destructuring syntax. This is great for bringing tuple-esque operations to the language.

It doesn't bring tuple-esque operations to the language; it's a shorter alternate syntax for the already existing "list()" destructuring syntax.
Post reply on HN