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

Mon Jan 17 00:36:54 PST 2011

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

--- Comment #5 from Gavin Barraclough <barraclough at apple.com>  2011-01-17 00:36:54 PST ---
(In reply to comment #4)
> It would be excellent to make a coordinated removal from JSC, SpiderMonkey, and V8. I think Opera folks have said they will go along too. Thoughts?

Sounds like a good change, and it would be great to coordinate this.

> 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?  I believe FireFox 3 was released mid-2008, FireFox 3.5 was released mid-2009, FireFox 4 is in beta now - so I'm reading "after Firefox 4" as meaning "actually shipping to end users some time in 2012."  Am I in the right ballpark here?

> 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.

I can't think of too many problems with this.  One issue would be if the call came from host code instead of JS code - e.g. "[].sort(/a/)".  In these cases do you think you would:
 * try to trace back up the call stack to the next non-host scope, and check if this is strict.
 * assume the caller to be non-strict (allow the call).
 * or treat all host code as strict (throw).
or some other resolution I'm not thinking of. :-)

(I'm not sure if there are any host functions where it is particularly useful to pass a RegExp as a callback, so I guess this is probably somewhat moot anyway).

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