rfc:empty_isset_exprs

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision		Previous revision
Next revisionBoth sides next revision
rfc:empty_isset_exprs [2012/04/12 21:39] – created nikicrfc:empty_isset_exprs [2012/04/19 10:06] – nikic
Line 2: Line 2:
   * Date: 2012-04-12   * Date: 2012-04-12
   * Author: Nikita Popov <nikic@php.net>   * Author: Nikita Popov <nikic@php.net>
-  * Status: Under Discussion+  * Status: In voting phase 
 +  * Original discussion: http://markmail.org/thread/gnci76ugtwda2t42 (Apr 10, 2012 3:53 pm) 
 +  * RFC announcement: http://markmail.org/thread/ju2jyrenxkeddrnt (Apr 12, 2012 2:42 pm)
  
 ==== Summary ==== ==== Summary ====
Line 23: Line 25:
  
 As for function calls (and other expressions) it is already known that the value exists, using ''empty()''/''isset()'' is As for function calls (and other expressions) it is already known that the value exists, using ''empty()''/''isset()'' is
-not necessary and ''!func()''/''func() !== null'' can be used instead instead.+not necessary and ''!func()''/''func() !== null'' can be used instead.
  
 ==== Why should we change the behavior? ==== ==== Why should we change the behavior? ====
Line 37: Line 39:
  
 The patch is available as a PR on Github: https://github.com/php/php-src/pull/54 The patch is available as a PR on Github: https://github.com/php/php-src/pull/54
 +
 +==== Vote ====
 +
 +<doodle 
 +title="Should empty() and isset() accept arbitrary arguments?" auth="nikic" voteType="single" closed="False">
 +   * yes
 +   * no
 +</doodle>
rfc/empty_isset_exprs.txt · Last modified: 2017/09/22 13:28 by 127.0.0.1

Page Tools