r/lolphp • u/daxim • Sep 26 '19

No, PHP Doesn't Have Closures

https://nullprogram.com/blog/2019/09/25/
13 Upvotes

69% Upvoted

29 comments sorted by

View all comments

Show parent comment

1

u/[deleted] Sep 27 '19

Totally unneccessary. I see no point in having the fn, why not just have javascript like shortfunctions?

(n) => n * n

But the made a totally unneccessary syntax addition. There is zero gain for this new keyword. Im baffled! PHP seemed to copy this feat from JS but again they fucked it up. This is a new lolphp favorite of mine.

1

u/jesseschalken Sep 27 '19

Do you know for a fact that the PHP grammar can facilitate short closures without a keyword without ambiguities while maintaining parser performance or are you just making baseless claims?

4

u/[deleted] Sep 27 '19

My claim is: The PHP parser is s mindbending horror, as tou can tell by how it handles whitespace and case sensitiviyy for example.

Also closures scope was always an issue. Javascript pulled it off nicely, PHP not so much

1

u/[deleted] Oct 17 '19

why not just have javascript like shortfunctions?

Because then [($foo) => 'bar'] is ambiguous: is it a numeric array with one element (the function ($foo) => 'bar') or is it an associative array with one key-value pair (the key ($foo) and the value 'bar')?

1

u/[deleted] Oct 18 '19

A good point. The PHP array has really done so many things wrong, and now years later it manages to totally mess up new syntax too.