[wp-trac] [WordPress Trac] #10493: Allow closures as callbacks

[WordPress Trac]

#10493: Allow closures as callbacks
-------------------------+--------------------------------------------------
 Reporter:  scribu       |       Owner:  scribu          
     Type:  enhancement  |      Status:  new             
 Priority:  normal       |   Milestone:  3.0             
Component:  Plugins      |     Version:  2.9             
 Severity:  normal       |    Keywords:  has-patch commit
-------------------------+--------------------------------------------------
Changes (by dd32):

  * keywords:  has-patch => has-patch commit
  * component:  General => Plugins
  * milestone:  Future Release => 3.0


Comment:

 > When 5.3 is minimum system requirement than every coder can actually use
 cosures because of the system requirements.

 A lot of people ignore the WP Minimum requirements, Plugin authors and
 those of us who use WordPress as a base for other projects have the right
 to require other minium requirements. PHP5+ is a very common Plugin rule.
 PHP 5.3+ is perfectly respectable for other projects due to PHP-
 functionalities.

 > I mean this trac is about the core code, right?

 Trac is about the Core code, Its the place people come to get Enhancements
 and defects fixed. Just because something is made theoretically possible,
 it doesnt mean that everyone has to use it.

 > I could open tickets that showcase the possibilities we get with PHP 5
 regarding objects, visibility and inheritance, exceptions and interfaces -
 something infact I already use in plugins w/o boosting the requirements
 too much.

 Theres the difference, That requires changes to WordPress which raise
 WordPress's minimum requirement. This does not. WordPress can stay as PHP
 4.3+, But allows Plugin authors to seemlessly use PHP5.3 functionality
 '''if they have support for it in their php'''.

 just FYI, WordPress already has bit of PHP5+-only code, its just disabled
 on those with older installs. If its possible to enable more
 functionalities, without affecting core in a negitive way, then why should
 it be rejected.

 As westi said earlier, We dont -need- this, But it does no harm, and for
 those who integrate WordPress into other projects, This allows them to use
 a functionality which they may use themselves.

 Listing this for 3.0 as a commit candidate.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/10493#comment:13>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software