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

Re: How to correctly spec sequences requiring an iterable

From: Allen Wirfs-Brock <allen@wirfs-brock.com>
Date: Fri, 15 Nov 2013 09:37:30 -0800
Cc: Jason Orendorff <jason.orendorff@gmail.com>, Boris Zbarsky <bzbarsky@mit.edu>, "public-script-coord@w3.org" <public-script-coord@w3.org>
Message-Id: <679CF30C-400E-4E91-BDF1-D1C8EC29E138@wirfs-brock.com>
To: Domenic Denicola <domenic@domenicdenicola.com>
Some people prefer to use an explicit null to state that they really mean "not the normal object value" rather than the bit more sloppy use of undefined.  I happy to define things in a way that accommodates that either style.


On Nov 15, 2013, at 9:33 AM, Domenic Denicola wrote:

> From: Allen Wirfs-Brock <allen@wirfs-brock.com>
>> If iteratorGetter is undefined or null then let usingIterator be false; otherwise let usingIterator be true.
> Why "or null"? I would expect one of these two alternatives:
> 1. undefined => usingIterator = false; otherwise, true
> 2. callable => usingIterator = true; otherwise, false
Received on Friday, 15 November 2013 17:38:05 UTC

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