W3C home > Mailing lists > Public > public-script-coord@w3.org > January to March 2012

[Bug 16075] Make a float/double type that excludes NaN/Infinity/-Infinity

From: <bugzilla@jessica.w3.org>
Date: Tue, 06 Mar 2012 01:45:29 +0000
To: public-script-coord@w3.org
Message-Id: <E1S4jSz-0006T0-CD@jessica.w3.org>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16075

Cameron McCormack <cam@mcc.id.au> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED

--- Comment #6 from Cameron McCormack <cam@mcc.id.au> 2012-03-06 01:45:27 UTC ---
I went with removing the non-finite values from float and double, and
introducing two new types "unrestricted float" and "unrestricted double" which
do have those values.  I noted these new types as being "at risk", in case we
don't have any uses for them.  When passing non-finite values to an object
expecting a float/double, a TypeError is thrown.  I haven't added an extended
attribute for the "ignore the function call instead of throwing" for canvas; I
think we can just have those the relevant functions take "unrestricted float"s
and keep defining their special behaviour in those cases.

http://dev.w3.org/cvsweb/2006/webapi/WebIDL/Overview.xml.diff?r1=1.473;r2=1.474;f=h

Let me know if this resolution is satisfactory, thanks.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Tuesday, 6 March 2012 01:45:32 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 May 2013 19:30:05 UTC