Changes between Version 3 and Version 4 of WG1Ballot5Results
 Timestamp:
 04/09/12 07:46:13 (5 years ago)
Legend:
 Unmodified
 Added
 Removed
 Modified

WG1Ballot5Results
v3 v4 89 89 * [wiki:WG1BallotLucier Lucier]: yes 90 90 * [wiki:WG1BallotMedernach Medernach]: yes 91 * [wiki:WG1BallotShinn Shinn]: no 91 92 * [wiki:WG1BallotSnellPym SnellPym]: yes, no 92 93 * '''Results:''' '''yes''', no 93 * '''Ratios:''' 6: 194 * '''Ratios:''' 6:2 94 95 * '''Rationales:''' 95 96 … … 102 103 `Medernach`:: 103 104 The sign bit of `NaNs` is meaningless in the IEEE Standard 754 floatingpoint formats, but in order to avoid using it as an identifier we may consider both as synonymous. However I really would prefer using `NaN` instead of `+nan.0` or `nan.0` (as it is not a number but an indication of failure, to help diagnostic, it is neither signed in general, nor exact nor inexact, isn't it ?) 105 `Shinn`:: 106 I don't understand the motivation behind this. NaN can neither be positive nor negative  the "+" is just a hint that the value is numeric (which is no longer true with the symbol extensions that now allow an initial "+"). Thus "" serves no purpose and does not simplify the syntax  if we allow multiple forms, do we also allow "nan.0", "+nan.", "+nan", "+nan.1", etc.? One is easier to remember than two. 104 107 105 108 === #278 Shrink division routines to just truncate and floor === … … 118 121 Vote `shrink` to prune to `truncate*` (R5RS) and `floor*` (R5RS `modulo`), moving 119 122 the extra operators to the large language; `shrink/core` to do the same as `shrink` 120 but move the remaining operators to the core language; or ` 1` to keep all 18123 but move the remaining operators to the core language; or `keep` to keep all 18 121 124 division operators in the small language. 122 125