[html5] r3528 - [e] (0) Clean up some of the conventions around Infinity and NaN.

whatwg at whatwg.org whatwg at whatwg.org
Mon Aug 3 00:16:22 PDT 2009


Author: ianh
Date: 2009-08-03 00:16:20 -0700 (Mon, 03 Aug 2009)
New Revision: 3528

Modified:
   index
   source
Log:
[e] (0) Clean up some of the conventions around Infinity and NaN.

Modified: index
===================================================================
--- index	2009-08-03 07:00:38 UTC (rev 3527)
+++ index	2009-08-03 07:16:20 UTC (rev 3528)
@@ -2125,14 +2125,14 @@
     required for conforming IDL fragments, as described in the Web IDL
     specification. <a href=#refsWEBIDL>[WEBIDL]</a></p>
 
-    <p>Unless otherwise specified, if a DOM attribute that is a
-    floating point number type (<code title="">float</code>) is
-    assigned an Infinity or Not-a-Number value, a
+    <p id=float-nan>Unless otherwise specified, if a DOM attribute
+    that is a floating point number type (<code title="">float</code>)
+    is assigned an Infinity or Not-a-Number (NaN) value, a
     <code><a href=#not_supported_err>NOT_SUPPORTED_ERR</a></code> exception must be raised.</p>
 
     <p>Unless otherwise specified, if a method with an argument that
     is a floating point number type (<code title="">float</code>) is
-    passed an Infinity or Not-a-Number value, a
+    passed an Infinity or Not-a-Number (NaN) value, a
     <code><a href=#not_supported_err>NOT_SUPPORTED_ERR</a></code> exception must be raised.</p>
 
    </dd>
@@ -2598,7 +2598,8 @@
   number if there is one). If there is no E, then the exponent is
   treated as zero.</p>
 
-  <p class=note>The values ±Infinity and NaN are not <a href=#valid-floating-point-number title="valid floating point number">valid floating point
+  <p class=note>The Infinity and Not-a-Number (NaN) values are not
+  <a href=#valid-floating-point-number title="valid floating point number">valid floating point
   numbers</a>.</p>
 
   <div class=impl>
@@ -5294,8 +5295,9 @@
   of the floating point number</a> and then that string must be
   used as the new content attribute value.</p>
 
-  <p class=note>The values ±Infinity and NaN throw an
-  exception on setting, as defined by Web IDL. <a href=#refsWEBIDL>[WEBIDL]</a></p>
+  <p class=note>The values Infinity and Not-a-Number (NaN) values
+  throw an exception on setting, as <a href=#float-nan>defined
+  earlier</a>.</p>
 
   <p>If a reflecting DOM attribute is of the type
   <code><a href=#domtokenlist-0>DOMTokenList</a></code> or <code><a href=#domsettabletokenlist-0>DOMSettableTokenList</a></code>, then
@@ -23439,9 +23441,9 @@
   before they are composited onto the canvas. The value must be in the
   range from 0.0 (fully transparent) to 1.0 (no additional
   transparency). If an attempt is made to set the attribute to a value
-  outside this range (including Infinity and NaN values), the
-  attribute must retain its previous value. When the context is
-  created, the <code title=dom-context-2d-globalAlpha><a href=#dom-context-2d-globalalpha>globalAlpha</a></code> attribute must
+  outside this range, including Infinity and Not-a-Number (NaN)
+  values, the attribute must retain its previous value. When the
+  context is created, the <code title=dom-context-2d-globalAlpha><a href=#dom-context-2d-globalalpha>globalAlpha</a></code> attribute must
   initially have the value 1.0.</p>
 
   <p>The <dfn id=dom-context-2d-globalcompositeoperation title=dom-context-2d-globalCompositeOperation><code>globalCompositeOperation</code></dfn>
@@ -38402,11 +38404,11 @@
 
   <p>Where the above requirements say that a value is to be a number,
   the user agent must first apply the ToNumber() conversion operator
-  to the value, and then verify that the result is neither the
-  not-a-number NaN value nor an infinite value. If this result is
-  indeed acceptable (i.e. finite), the user agent must use the result
-  in the rest of the algorithm as if it had that had been the value
-  passed to the method. <a href=#refsECMA262>[ECMA262]</a></p>
+  to the value, and then verify that the result is neither an Infinity
+  value nor a Not-a-Number (NaN) value. If this result is indeed
+  acceptable (i.e. finite), the user agent must use the result in the
+  rest of the algorithm as if it had that had been the value passed to
+  the method. <a href=#refsECMA262>[ECMA262]</a></p>
 
   <p>Where the above requirements say that a value is to be an
   integer, the user agent must first apply the ToNumber() conversion
@@ -48405,9 +48407,8 @@
    <li><p>Apply the ToNumber() conversion operator to <var title="">timeout</var>, and let <var title="">timeout</var> be the
    result.</li>
 
-   <li><p>If <var title="">timeout</var> is not a number (NaN), not
-   finite (Infinity), or negative, let <var title="">timeout</var> be
-   zero.</li>
+   <li><p>If <var title="">timeout</var> is an Infinity value, a
+   Not-a-Number (NaN) value, or negative, let <var title="">timeout</var> be zero.</li>
 
    <li><p>Round <var title="">timeout</var> down to the nearest
    integer, and let <var title="">timeout</var> be the

Modified: source
===================================================================
--- source	2009-08-03 07:00:38 UTC (rev 3527)
+++ source	2009-08-03 07:16:20 UTC (rev 3528)
@@ -1171,14 +1171,14 @@
     required for conforming IDL fragments, as described in the Web IDL
     specification. <a href="#refsWEBIDL">[WEBIDL]</a></p>
 
-    <p>Unless otherwise specified, if a DOM attribute that is a
-    floating point number type (<code title="">float</code>) is
-    assigned an Infinity or Not-a-Number value, a
+    <p id="float-nan">Unless otherwise specified, if a DOM attribute
+    that is a floating point number type (<code title="">float</code>)
+    is assigned an Infinity or Not-a-Number (NaN) value, a
     <code>NOT_SUPPORTED_ERR</code> exception must be raised.</p>
 
     <p>Unless otherwise specified, if a method with an argument that
     is a floating point number type (<code title="">float</code>) is
-    passed an Infinity or Not-a-Number value, a
+    passed an Infinity or Not-a-Number (NaN) value, a
     <code>NOT_SUPPORTED_ERR</code> exception must be raised.</p>
 
    </dd>
@@ -1708,8 +1708,8 @@
   number if there is one). If there is no E, then the exponent is
   treated as zero.</p>
 
-  <p class="note">The values ±Infinity and NaN are not <span
-  title="valid floating point number">valid floating point
+  <p class="note">The Infinity and Not-a-Number (NaN) values are not
+  <span title="valid floating point number">valid floating point
   numbers</span>.</p>
 
   <div class="impl">
@@ -5006,9 +5006,9 @@
   of the floating point number</span> and then that string must be
   used as the new content attribute value.</p>
 
-  <p class="note">The values ±Infinity and NaN throw an
-  exception on setting, as defined by Web IDL. <a
-  href="#refsWEBIDL">[WEBIDL]</a></p>
+  <p class="note">The values Infinity and Not-a-Number (NaN) values
+  throw an exception on setting, as <a href="#float-nan">defined
+  earlier</a>.</p>
 
   <p>If a reflecting DOM attribute is of the type
   <code>DOMTokenList</code> or <code>DOMSettableTokenList</code>, then
@@ -25485,9 +25485,9 @@
   before they are composited onto the canvas. The value must be in the
   range from 0.0 (fully transparent) to 1.0 (no additional
   transparency). If an attempt is made to set the attribute to a value
-  outside this range (including Infinity and NaN values), the
-  attribute must retain its previous value. When the context is
-  created, the <code
+  outside this range, including Infinity and Not-a-Number (NaN)
+  values, the attribute must retain its previous value. When the
+  context is created, the <code
   title="dom-context-2d-globalAlpha">globalAlpha</code> attribute must
   initially have the value 1.0.</p>
 
@@ -43157,11 +43157,11 @@
 
   <p>Where the above requirements say that a value is to be a number,
   the user agent must first apply the ToNumber() conversion operator
-  to the value, and then verify that the result is neither the
-  not-a-number NaN value nor an infinite value. If this result is
-  indeed acceptable (i.e. finite), the user agent must use the result
-  in the rest of the algorithm as if it had that had been the value
-  passed to the method. <a href="#refsECMA262">[ECMA262]</a></p>
+  to the value, and then verify that the result is neither an Infinity
+  value nor a Not-a-Number (NaN) value. If this result is indeed
+  acceptable (i.e. finite), the user agent must use the result in the
+  rest of the algorithm as if it had that had been the value passed to
+  the method. <a href="#refsECMA262">[ECMA262]</a></p>
 
   <p>Where the above requirements say that a value is to be an
   integer, the user agent must first apply the ToNumber() conversion
@@ -55094,9 +55094,9 @@
    title="">timeout</var>, and let <var title="">timeout</var> be the
    result.</p></li>
 
-   <li><p>If <var title="">timeout</var> is not a number (NaN), not
-   finite (Infinity), or negative, let <var title="">timeout</var> be
-   zero.</p></li>
+   <li><p>If <var title="">timeout</var> is an Infinity value, a
+   Not-a-Number (NaN) value, or negative, let <var
+   title="">timeout</var> be zero.</p></li>
 
    <li><p>Round <var title="">timeout</var> down to the nearest
    integer, and let <var title="">timeout</var> be the




More information about the Commit-Watchers mailing list