rfc:precise_float_value
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
rfc:precise_float_value [2016/02/10 05:56] – yohgaki | rfc:precise_float_value [2017/09/22 13:28] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== PHP RFC: More precise float value handling ====== | ====== PHP RFC: More precise float value handling ====== | ||
- | * Version: | + | * Version: |
* Date: 2015-07-30 | * Date: 2015-07-30 | ||
- | * Author: Yasuo Ohgaki < | + | * Author: Yasuo Ohgaki < |
- | * Status: | + | * Status: |
* First Published at: http:// | * First Published at: http:// | ||
===== Introduction ===== | ===== Introduction ===== | ||
- | This RFC is based on float like JSON numeric | + | This RFC is based on the discussion |
- | JSON is used to exchange data between systems. Although [[https:// | + | JSON is used to exchange data between systems. Although [[https:// |
- | Currently, json_encode() uses EG(precision) which is 14. IEEE 754 double supports | + | Currently json_encode() uses EG(precision) which is set to 14. That means that 14 digits at most are used for displaying (printing) the number. IEEE 754 double supports |
<code php> | <code php> | ||
Line 40: | Line 40: | ||
</ | </ | ||
- | PHP's float type stores " | + | PHP's float type stores " |
Current PHP outputs meaningless values for oversized EG(precision)/ | Current PHP outputs meaningless values for oversized EG(precision)/ | ||
Line 57: | Line 57: | ||
float(0.12345678901234567736988623209981597028672695159912109375) | float(0.12345678901234567736988623209981597028672695159912109375) | ||
</ | </ | ||
+ | |||
+ | That is caused by used mode for double to string conversion. | ||
===== Proposal ===== | ===== Proposal ===== | ||
- | * PHP 7.1: Introduce | + | This RFC proposes to introduce a new setting |
- | + | ||
- | Since JSON is used extensively for web apps, we may have JSON specific INI setting for better compatibility and ease of use. | + | |
- | + | ||
- | * PHP 7.1: Add JSON_G(json_precision) - Add JSON module specific precision INI setting. | + | |
- | + | ||
- | PHP 5.6/ | + | |
- | + | ||
- | * PHP 5.6/7.0: Make json_encode() uses PG(serialize_precision). | + | |
+ | The RFC also proposes changing ini for JSON precision to PG(serialize_precision). | ||
Followings are sample codes and outputs of the proposed patch. | Followings are sample codes and outputs of the proposed patch. | ||
Line 80: | Line 75: | ||
ini_set(' | ini_set(' | ||
ini_set(' | ini_set(' | ||
- | ini_set(' | ||
var_dump($v); | var_dump($v); | ||
Line 103: | Line 97: | ||
ini_set(' | ini_set(' | ||
ini_set(' | ini_set(' | ||
- | ini_set(' | ||
var_dump($v); | var_dump($v); | ||
echo var_export($v, | echo var_export($v, | ||
+ | ini_set(' | ||
echo json_encode($v), | echo json_encode($v), | ||
+ | ini_set(' | ||
echo $v, PHP_EOL; | echo $v, PHP_EOL; | ||
?> | ?> | ||
Line 123: | Line 118: | ||
===== Backward Incompatible Changes ===== | ===== Backward Incompatible Changes ===== | ||
- | PHP 7.1 will have 0 mode as the default. var_export()/ | + | Setting |
- | FYI: Existing | + | The BC break could happen only if someone would rely on exact output but that shouldn' |
None when old INI value is used. | None when old INI value is used. | ||
Line 131: | Line 126: | ||
===== Proposed PHP Version(s) ===== | ===== Proposed PHP Version(s) ===== | ||
- | * PHP 7.1.0 - EG(precision)/ | + | * PHP 7.1 |
- | * PHP 5.6.x/7.0.0 - JSON uses PG(serialize_precision) for float precision. | + | |
===== RFC Impact ===== | ===== RFC Impact ===== | ||
Line 142: | Line 136: | ||
* 0 mode (EG(precision)= -1) float outputs values rounded to nearest. | * 0 mode (EG(precision)= -1) float outputs values rounded to nearest. | ||
- | Standard module | + | Standard module |
- | * serialize(), | + | * serialize(), |
- | + | ||
- | JSON | + | |
- | * json_encode() - PHP7.1: | + | |
==== To Opcache ==== | ==== To Opcache ==== | ||
Line 164: | Line 154: | ||
* php.ini-production values : 14 Unmodified | * php.ini-production values : 14 Unmodified | ||
- | serialize_precision(PHP5.6/ | + | serialize_precision |
- | * hardcoded default values : 17 Unmodified | + | |
- | * php.ini-development values : 17 Unmodified | + | |
- | * php.ini-production values : 17 Unmodified | + | |
- | + | ||
- | serialize_precision(PHP7.1) | + | |
- | * hardcoded default values : -1 | + | |
- | * php.ini-development values : -1 | + | |
- | * php.ini-production values : -1 | + | |
- | + | ||
- | json.precision(NEW - PHP7.1 only) | + | |
* hardcoded default values : -1 | * hardcoded default values : -1 | ||
* php.ini-development values : -1 | * php.ini-development values : -1 | ||
Line 190: | Line 170: | ||
===== Future Scope ===== | ===== Future Scope ===== | ||
- | |||
- | * Remove PG(serialize_precision) setting. If we are going to remove PG(serialize_precision) in the future, we may be better to have JSON_G(json_precision) as one may need specific precision for JSON data. | ||
WDDX | WDDX | ||
Line 200: | Line 178: | ||
- | ===== Proposed | + | ===== Voting ===== |
- | Requires a 50%+1 majority | + | Requires a 2/3 majority for the first vote (mode 0 to become default for serialize precision) and 50%+1 majority |
- | Please choose | + | The both votes are straight |
- | <doodle title=" | + | <doodle title=" |
* Yes | * Yes | ||
* No | * No | ||
</ | </ | ||
- | . | + | <doodle title=" |
- | + | ||
- | Please choose your preference whether JSON module should use PG(serialize_precision) | + | |
- | + | ||
- | <doodle title=" | + | |
* Yes | * Yes | ||
* No | * No | ||
</ | </ | ||
- | . | + | The votes started on 2016-06-12 at 19:00 UTC and ended on 2016-06-19 at 19:00 UTC. |
- | Please choose if PHP 5.6's JSON should use PG(serialize_precision) or EG(precision). Currently it uses EG(precision). | + | ===== Patches and Tests ===== |
- | <doodle title=" | + | The initial PR can be found here: |
- | * Yes | + | |
- | * No | + | |
- | </ | + | |
- | Please choose if PHP 7.0's JSON should use PG(serialize_precision) or EG(precision). Currently it uses EG(precision). | + | * https:// |
- | <doodle title=" | + | Note that the PR is currently outdated but it will be updated if the RFC is accepted. |
- | * Yes | + | |
- | * No | + | |
- | </ | + | |
+ | ===== Implementation ===== | ||
+ | Merged into php-src for PHP 7.1: https:// | ||
- | ===== Patches and Tests ===== | ||
- | |||
- | * https:// | ||
- | |||
- | ===== Implementation ===== | ||
After the project is implemented, | After the project is implemented, | ||
- | - the version(s) it was merged to | ||
- | - a link to the git commit(s) | ||
- a link to the PHP manual entry for the feature | - a link to the PHP manual entry for the feature | ||
Line 252: | Line 215: | ||
* https:// | * https:// | ||
* https:// | * https:// | ||
+ | * http:// | ||
===== Rejected Features ===== | ===== Rejected Features ===== | ||
- | Keep this updated with features that were discussed on the mail lists. | + | |
+ | None | ||
rfc/precise_float_value.1455083794.txt.gz · Last modified: 2017/09/22 13:28 (external edit)