W3C home > Mailing lists > Public > www-dom@w3.org > July to September 2001

Re: hasFeature and ECMAScript

From: Fred L. Drake, Jr. <fdrake@acm.org>
Date: Thu, 12 Jul 2001 18:46:10 -0400 (EDT)
Message-ID: <15182.10418.802513.906264@cj42289-a.reston1.va.home.com>
To: Thomas Much <thomas@snailshell.de>
Cc: <www-dom@w3.org>

Joseph Kesselman wrote:
 > I'd say that's a binding issue -- "what does null mean in this binding"

Thomas Much writes:
 > null and undefined are two different values in ECMAScript, so this could be
 > somewhat dangerous (both values evaluate to boolean false, but if an

  This is a matter of the binding.  It sounds to me like the only
reasonable way to do this is to bind the IDL null value to the
ECMAScript null value; undefined is a different concept.  Since the
issue doesn't appear to be the value assigned to parameters omitted by
the caller, since the DOM doesn't describe any optional parameters,
there's no clear need to accept the undefined value.

 > But if null is an input parameter and it is not used to specify an empty
 > reference but an unspecified value, an ECMAScript programmer should be
 > allowed to pass undefined as well, because "undefined" is in ECMAScript

  But there are no unspecified values in the DOM specifications,
except where the specs are still being written.  Or at least I haven't
noticed that situation.


  -Fred

-- 
Fred L. Drake, Jr.  <fdrake at acm.org>
PythonLabs at Digital Creations
Received on Thursday, 12 July 2001 18:48:11 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 22 June 2012 06:13:49 GMT