Comments on: What’s wrong with PHP closures?

By: Pawel

Pawel — Sun, 04 Sep 2011 15:07:54 +0000

This kind of syntax would be nice, but… it’s still the good old PHP :)

By: Thibaut Assus

Thibaut Assus — Wed, 31 Aug 2011 08:47:48 +0000

Amazing, I searched a way of doing that kind of stuff in PHP !
Thank you very much for helping me with this old language !

Do you think we could create arrays declaratively like :
[2, 3] and change the -> in . ?
and remove this crappy useless $ ?
so we could do : [2, 3].map(function(x) {return x + 2;});

By: Jason

Jason — Tue, 29 Mar 2011 21:38:27 +0000

Your use of closures is very similar to what one would do in Haskell or Scheme: use an anonymous function (lambda) as an argument to some higher order function.

By: Pawel

Pawel — Fri, 08 Oct 2010 08:24:36 +0000

I wouldn’t call it obsession, but the less code you have to look at, debug and work with, the better :)

By: Some Guy

Some Guy — Fri, 08 Oct 2010 00:27:26 +0000

Why is everyone obsessed with these one-liners? If reducing the amount of typing is the main goal, then I would just use Ruby On Rails. PHP is for speed, not to be pretty.

By: [转]谈PHP 闭包特性在实际应用中的问题 - 沉夜集

[转]谈PHP 闭包特性在实际应用中的问题 - 沉夜集 — Mon, 26 Apr 2010 05:19:17 +0000

[...] 原文链接： http://justafewlines.com/2009/10/whats-wrong-with-php-closures/ [...]

By: zhongkun » 谈PHP 闭包特性在实际应用中的问题

zhongkun » 谈PHP 闭包特性在实际应用中的问题 — Mon, 14 Dec 2009 10:46:13 +0000

[...] 原文链接： http://justafewlines.com/2009/10/whats-wrong-with-php-closures/ [...]

By: Pawel

Pawel — Tue, 03 Nov 2009 17:29:16 +0000

Hey Sam,

Yeah I read that Wiki. The problem is, they added closures, but it seems like it’s only because it’s trendy and cool these days (groovy, ruby, scala, everyone has them). As a result, the feature is there, but it’s cumbersome to use.

> PHP has always resisted allow you to have
> two ways of doing the same action.

PHP is built incrementally, features are just tossed in randomly (at least it seems so sometimes), so redundant functionality is very common. Just take a look at PHP function list…

Personally, I think they did closures this way because it was easier. Otherwise, they’d have to improve PHP parser, and that’s why we got this clumsy syntax.

At least we can forget about create_function, which is obviously a good thing :)

By: Sam Hennessy

Sam Hennessy — Tue, 03 Nov 2009 00:26:22 +0000

Sorry for the late comment.

Your correct in your observations of PHP, but you missed the reason my these features were added. (http://wiki.php.net/rfc/closures)

It was intended to clean up some issues with current use of things like create_function (http://us2.php.net/create_function).

PHP has always resisted allow you to have two ways of doing the same action. This is part of PHP’s intentions of an easy language to learn.

So while your correct, I feel you’ve left out the reasons why it was done that way.

By: Pawel

Pawel — Mon, 02 Nov 2009 17:04:16 +0000

Thanks :)

I wish I had more time to post…