rfc:trailing_whitespace_numerics

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
rfc:trailing_whitespace_numerics [2019/02/07 01:42] – > ajfrfc:trailing_whitespace_numerics [2019/03/04 22:14] – ajf
Line 46: Line 46:
 The hope is that the backwards compatibility impact would be limited by Part 1's acceptance of trailing whitespace, since that would prevent a large category of currently non-well-formed strings from being affected. The hope is that the backwards compatibility impact would be limited by Part 1's acceptance of trailing whitespace, since that would prevent a large category of currently non-well-formed strings from being affected.
  
-In order to prepare for the backwards-compatibility break in the following major version, the “A non well formed numeric value encountered” notice (where currently produced) should be changed in the PHP 7.x (currently PHP 7.4) to mention that this behaviour is deprecated, i.e. ”A non well formed numeric value encountered (non well formed numeric values are deprecated and will be considered non-numeric in PHP 8.0)”.+In order to prepare for the backwards-compatibility break in the following major version, the “A non well formed numeric value encountered” notice (where currently produced) should be changed in the next PHP 7.x (currently PHP 7.4) to mention that this behaviour is deprecated, i.e. ”A non well formed numeric value encountered (non well formed numeric values are deprecated and will be considered non-numeric in PHP 8.0)”.
  
 For the PHP interpreter, this change would be accomplished by modifying the ''is_numeric_string'' C function (and its variants) in the Zend Engine. This would therefore affect PHP features which make use of this function, including: For the PHP interpreter, this change would be accomplished by modifying the ''is_numeric_string'' C function (and its variants) in the Zend Engine. This would therefore affect PHP features which make use of this function, including:
Line 56: Line 56:
 It would not affect the following features, since they already treat non-well-formed numeric strings strictly: It would not affect the following features, since they already treat non-well-formed numeric strings strictly:
  
-  * The comparison operators 
   * The <php>\is_numeric</php> function   * The <php>\is_numeric</php> function
   * The <php>++</php> and <php>--</php> operators   * The <php>++</php> and <php>--</php> operators
 +
 +TBD: comparison operators 
  
 TBD: what about explicit conversions, though? TBD: what about explicit conversions, though?
rfc/trailing_whitespace_numerics.txt · Last modified: 2020/07/23 21:50 by ajf

Page Tools