rfc:empty_isset_exprs
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
rfc:empty_isset_exprs [2012/04/19 10:06] – nikic | rfc:empty_isset_exprs [2012/05/13 12:47] – Close voting nikic | ||
---|---|---|---|
Line 15: | Line 15: | ||
but it is not possible to write '' | but it is not possible to write '' | ||
- | Trying to do so results in this not pariculary | + | Trying to do so results in this not particularly |
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 39: | Line 39: | ||
The patch is available as a PR on Github: https:// | The patch is available as a PR on Github: https:// | ||
+ | |||
+ | ==== Change only empty()? ==== | ||
+ | |||
+ | After further discussion it seems like it might be better to only add expression support for '' | ||
+ | original RFC included '' | ||
+ | |||
+ | On the other hand, using '' | ||
+ | is semantically unclear (how can '' | ||
+ | |||
+ | Allowing '' | ||
==== Vote ==== | ==== Vote ==== | ||
< | < | ||
- | title=" | + | title=" |
+ | * Both empty() and isset() | ||
+ | * Only empty() | ||
+ | * None | ||
+ | </ | ||
+ | |||
+ | The previous vote is obsolete and is left here only for reference: | ||
+ | |||
+ | <doodle | ||
+ | title=" | ||
* yes | * yes | ||
* no | * no | ||
</ | </ |
rfc/empty_isset_exprs.txt · Last modified: 2017/09/22 13:28 by 127.0.0.1