W3C home > Mailing lists > Public > public-script-coord@w3.org > October to December 2013

[Bug 23532] Dealing with undefined

From: <bugzilla@jessica.w3.org>
Date: Wed, 23 Oct 2013 21:03:27 +0000
To: public-script-coord@w3.org
Message-ID: <bug-23532-3890-gTwhhiFIAG@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23532

Joshua Bell <jsbell@google.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jsbell@google.com

--- Comment #22 from Joshua Bell <jsbell@google.com> ---
(In reply to Jonas Sicking from comment #21)
> For a function like "void func(double arg)"
> 
> A) Make both func() and func(undefined) throw TypeError.
> B) Make both func() and func(undefined) be equivalent to
>    func(ToNumber(undefined)), i.e. equivalent to func(NaN).
> 
> I even *think* WebKit (and thus Blink) has done B for a long time.

Assuming func is not overloaded, then in Blink (and WebKit last I knew) func()
throws TypeError but func(undefined) coerces.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Wednesday, 23 October 2013 21:03:30 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:18 UTC