[Webkit-unassigned] [Bug 28285] Remove non-spec support for callable RegExp

[bugzilla-daemon at webkit.org]

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





--- Comment #6 from Brendan Eich <brendan at mozilla.org>  2011-01-17 23:26:58 PST ---
(In reply to comment #5)
> > See Mozilla bug https://bugzilla.mozilla.org/show_bug.cgi?id=582717 -- we plan to remove support for callable RegExps after Firefox 4.
> 
> To help us understand the schedule, when do you see this appearing in shipping FireFox?

We're going to quarterly releases after Firefox 4, so mid-year. If too much web content depends on callable regexps, we'll have to rethink, but to get that signal we will disable callability in nightlies, soon (next month).

> > I may remove it from our ES5 strict mode implementation for Firefox 4.
> 
> This is interesting, I imagine we could probably do the same for consistency.  What are you thinking here? - from the [[Call]] method of the RegExp would you check the scope containing the call site to see if it was strict?  I think we could probably do the same.

It seems better to flag the regexp itself as strict, depending on how it was created. Strict code could still trampoline the RegExp constructor call off some non-strict code, but loss of strictness in the created regexp seems right in such cases.

/be

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.