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: Patrick Mueller <pmuellr@gmail.com>
Date: Mon, 6 Dec 2010 08:34:15 -0500
Message-ID: <AANLkTinHf+Hd9=7Yc=NgeuA7otTW32P+m1Ggspg_QVQe@mail.gmail.com>
To: Jeremy Orlow <jorlow@chromium.org>
Cc: Charles Pritchard <chuck@jumis.com>, public-webapps@w3.org
There was an attempt to fix this, in this WebKit bug:

   https://bugs.webkit.org/show_bug.cgi?id=32722

It's a JSC issue.  I'm not clear what the current status is of the JSC
parser.

On Mon, Dec 6, 2010 at 06:08, Jeremy Orlow <jorlow@chromium.org> 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
>>
>>
>


-- 
Patrick Mueller
http://muellerware.org
Received on Tuesday, 7 December 2010 10:17:17 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:42 GMT