W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2010

Re: continue as a reserved word and a conflict with IndexedDB

From: Oliver Hunt <oliver@apple.com>
Date: Mon, 6 Dec 2010 08:02:12 -0800
Cc: Charles Pritchard <chuck@jumis.com>, public-webapps@w3.org
Message-Id: <B5C1181D-8509-4376-9712-407094CB66B5@apple.com>
To: Jeremy Orlow <jorlow@chromium.org>
This should work fine in a nightly already, if it doesn't you need to file a bug.


On Dec 6, 2010, at 3:08 AM, Jeremy Orlow wrote:

> I'm pretty sure this was discussed and that EMCA5 does make it possible to use continue as we do.  At least that's the conclusion we had with delete.  My guess is that the JavaScriptCore (WebKit's main JavaScript engine) parser needs to be changed.  If so, you should probably file a bug at webkit.org.
> J
> On Mon, Dec 6, 2010 at 2:27 AM, Charles Pritchard <chuck@jumis.com> wrote:
> I just noticed that the cursor "continue" method in IndexedDB runs afoul of the Safari js parser, with "continue" being a reserved word.
> Was there any discussion on this issue? Should there be? Should I not worry about it, and use  cursor['continue'] instead of cursor.continue() ?
> -Charles

Received on Monday, 6 December 2010 16:02:43 UTC

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