rfc:string_to_number_comparison
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:string_to_number_comparison [2020/07/02 07:58] – nikic | rfc:string_to_number_comparison [2020/07/17 09:32] – nikic | ||
---|---|---|---|
Line 118: | Line 118: | ||
// Before | After | Type | // Before | After | Type | ||
var_dump(42 == " | var_dump(42 == " | ||
- | var_dump(42 == " | + | var_dump(42 == " |
var_dump(42 == " | var_dump(42 == " | ||
var_dump(42 == " | var_dump(42 == " | ||
var_dump( 0 == " | var_dump( 0 == " | ||
+ | // (*) Becomes well-formed if saner numeric strings RFC passes | ||
</ | </ | ||
- | A notable asymmetry under the new semantics is that '' | + | A notable asymmetry under the new semantics is that '' |
==== Precision ==== | ==== Precision ==== | ||
Line 171: | Line 172: | ||
This change to the semantics of non-strict comparisons is backwards incompatible. Worse, it constitutes a silent change in core language semantics. Code that worked one way in PHP 7.4 will work differently in PHP 8.0. Use of static analysis to detect cases that may be affected is likely to yield many false positives. | This change to the semantics of non-strict comparisons is backwards incompatible. Worse, it constitutes a silent change in core language semantics. Code that worked one way in PHP 7.4 will work differently in PHP 8.0. Use of static analysis to detect cases that may be affected is likely to yield many false positives. | ||
- | One possible way to mitigate | + | Testing with [[https:// |
===== Vote ===== | ===== Vote ===== | ||
- | TBD | + | Yes/No. |
rfc/string_to_number_comparison.txt · Last modified: 2020/07/31 12:55 by nikic