[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 #7 from Jeff Walden (remove +bwo to email) <jwalden+bwo at mit.edu>  2011-01-18 04:57:29 PST ---
(In reply to comment #6)
> > > 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.

Making regular expressions callable or not based on the creating code would seem to founder on the same concerns about knowing the strictness of the caller as did our bug to make parseInt ES5-compatible only when called from strict mode:

https://bugzilla.mozilla.org/show_bug.cgi?id=577536
https://bugzilla.mozilla.org/show_bug.cgi?id=583925

Or so it seems to me on first pale.

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