On Jul 2, 10:05 am, Attila Szegedi <[EMAIL PROTECTED]> wrote: > > > So what do we do in this case? It seems like we could extend Rhino to > > handle eval.call specially, much like eval is handled specially. That > > seems like a reasonable approach; would it solve your problem? > > Don't want to speak in John's name, but I think it would. eval.call > and eval.apply would help him achieve what he wanted, and we could > still keep the optimization. It's aliasing the eval that'd make the > optimization impossible... > > Attila.
We have a bug report (in the HtmlUnit project) where someone is complaining about not being able to alias eval (because all of the native browsers allow this). So for us, this partial fix wouldn't work. Any chance we can allow eval aliasing in interpreted mode (possibly subject to some FEATURE_XXX config)? _______________________________________________ dev-tech-js-engine-rhino mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-js-engine-rhino
