rfc:empty_isset_exprs

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revisionBoth sides next revision
rfc:empty_isset_exprs [2012/04/19 10:06] – nikicrfc:empty_isset_exprs [2012/04/30 12:49] – Change vote nikic
Line 15: Line 15:
 but it is not possible to write ''empty(foo())''. but it is not possible to write ''empty(foo())''.
  
-Trying to do so results in this not pariculary helpful error message: "Can't use function return value in write context".+Trying to do so results in this not particularly helpful error message: "Can't use function return value in write context".
  
 For other expressions (not variables and not function calls) a parse error is thrown. For other expressions (not variables and not function calls) a parse error is thrown.
Line 43: Line 43:
  
 <doodle  <doodle 
-title="Should empty() and isset() accept arbitrary arguments?" auth="nikic" voteType="single" closed="False">+title="Which of the language constructs should accept arbitrary arguments?" auth="nikic" voteType="single" closed="False"> 
 +   * Both empty() and isset() 
 +   * Only empty() 
 +   * None 
 +</doodle> 
 + 
 +The previous vote is obsolete and is left here only for reference: 
 + 
 +<doodle  
 +title="Should empty() and isset() accept arbitrary arguments?" auth="nikic" voteType="single" closed="True">
    * yes    * yes
    * no    * no
 </doodle> </doodle>
rfc/empty_isset_exprs.txt · Last modified: 2017/09/22 13:28 by 127.0.0.1

Page Tools