rfc:trailing_whitespace_numerics
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
rfc:trailing_whitespace_numerics [2019/03/06 00:03] – //// ajf | rfc:trailing_whitespace_numerics [2020/07/23 21:50] (current) – mark as superseded ajf | ||
---|---|---|---|
Line 2: | Line 2: | ||
* Version: 1.0 | * Version: 1.0 | ||
* Date: 2019-03-06 | * Date: 2019-03-06 | ||
- | * Author: Andrea Faulds, ajf@ajf.me | + | * Author: Andrea Faulds, |
- | * Status: | + | * Status: |
* First Published at: http:// | * First Published at: http:// | ||
Line 23: | Line 23: | ||
* < | * < | ||
- | * Arithmetic operations (e.g. < | + | * Arithmetic operations (e.g. < |
* When '' | * When '' | ||
* Type casts and other explicit conversions to integer or float (e.g. < | * Type casts and other explicit conversions to integer or float (e.g. < | ||
Line 35: | Line 35: | ||
The current behaviour of treating strings with leading whitespace as more numeric than strings with trailing whitespace is inconsistent and has no obvious benefit. It is an unintuitive, | The current behaviour of treating strings with leading whitespace as more numeric than strings with trailing whitespace is inconsistent and has no obvious benefit. It is an unintuitive, | ||
- | The inconsistency itself can require more work from the programmer. If rejecting number strings from user input that contain whitespace is useful to your application — perhaps it must be passed on to a back-end system that cannot handle whitespace — you cannot rely on e.g. < | + | The inconsistency itself can require more work from the programmer. If rejecting number strings from user input that contain whitespace is useful to your application — perhaps it must be passed on to a back-end system that cannot handle whitespace — you cannot rely on e.g. < |
Beyond the inconsistency, | Beyond the inconsistency, | ||
Line 81: | Line 81: | ||
If adopted, this would make Nikita Popov' | If adopted, this would make Nikita Popov' | ||
- | I would also plan a second RFC in a similar | + | I would also plan a second RFC in a similar |
===== Proposed Voting Choices ===== | ===== Proposed Voting Choices ===== | ||
Line 100: | Line 100: | ||
===== Changelog ===== | ===== Changelog ===== | ||
+ | * 2020-06-24: Take-over by George Peter Banyard with the consent of Andrea Faulds | ||
* 2019-03-06, v1.0: First non-draft version, dropped the second proposal from the RFC for now, I can make that as a follow-up RFC | * 2019-03-06, v1.0: First non-draft version, dropped the second proposal from the RFC for now, I can make that as a follow-up RFC | ||
* 2019-02-07 (draft): Added proposal to remove “non-well-formed” numeric strings at the suggestion of Nikita Popov, renamed to “Revise trailing character handling for numeric strings” | * 2019-02-07 (draft): Added proposal to remove “non-well-formed” numeric strings at the suggestion of Nikita Popov, renamed to “Revise trailing character handling for numeric strings” | ||
* 2017-01-18 (draft): First draft as “Permit trailing whitespace in numeric strings” | * 2017-01-18 (draft): First draft as “Permit trailing whitespace in numeric strings” |
rfc/trailing_whitespace_numerics.txt · Last modified: 2020/07/23 21:50 by ajf