rfc:string_to_number_comparison
Differences
This shows you the differences between two versions of the page.
Next revisionBoth sides next revision | |||
rfc:string_to_number_comparison [2019/02/26 09:03] – created nikic | rfc:string_to_number_comparison [2019/02/26 12:13] – Add PR link nikic | ||
---|---|---|---|
Line 2: | Line 2: | ||
* Date: 2019-02-26 | * Date: 2019-02-26 | ||
* Author: Nikita Popov < | * Author: Nikita Popov < | ||
- | * Status: | + | * Status: |
* Target Version: PHP 8.0 | * Target Version: PHP 8.0 | ||
+ | * Implementation: | ||
===== Introduction ===== | ===== Introduction ===== | ||
Line 187: | Line 188: | ||
===== Backward Incompatible Changes ===== | ===== Backward Incompatible Changes ===== | ||
- | 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 affect | + | 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 |
One possible way to mitigate the impact is to introduce an ini setting in PHP 7.4, which will perform the comparison using both the old and the new method and emit a deprecation warning if the results differ. This would allow identifying affected code based on production logs. | One possible way to mitigate the impact is to introduce an ini setting in PHP 7.4, which will perform the comparison using both the old and the new method and emit a deprecation warning if the results differ. This would allow identifying affected code based on production logs. |
rfc/string_to_number_comparison.txt · Last modified: 2020/07/31 12:55 by nikic