Re: length property value for functions with parameter enhancements

2011-08-27 Thread Andreas Rossberg
On 27 August 2011 00:34, Allen Wirfs-Brock al...@wirfs-brock.com wrote: Something we need to define for ES.next is how to compute the length property value for functions whose formal parameter list includes optional and/or rest parameters. True, and actually, there are more issues with length

double checking if window.eval(…) is an indirect call to eval().

2011-08-27 Thread John-David Dalton
So I have read the section (and the notes associated with it) over what a direct call to eval is: http://es5.github.com/#x15.1.2.1.1 http://dev.w3.org/html5/spec/Overview.html#script-s-global-object A direct call to the eval function is one that is expressed as a CallExpression that meets the

Re: double checking if window.eval(…) is an indirect call to eval().

2011-08-27 Thread Dmitry Soshnikov
On Sat, Aug 27, 2011 at 11:13 PM, John-David Dalton john.david.dal...@gmail.com wrote: So I have read the section (and the notes associated with it) over what a direct call to eval is: http://es5.github.com/#x15.1.2.1.1 http://dev.w3.org/html5/spec/Overview.html#script-s-global-object A

Re: double checking if window.eval(…) is an indirect call to eval().

2011-08-27 Thread Dmitry Soshnikov
On Sat, Aug 27, 2011 at 11:53 PM, John-David Dalton john.david.dal...@gmail.com wrote: No. It's the global object what is the base (more precisely, its DOM's proxy wrapper -- `window` or either the global itself), but not an environment record. So basically the only kind of

Re: double checking if window.eval(…) is an indirect call to eval().

2011-08-27 Thread Oliver Hunt
On Aug 27, 2011, at 2:42 PM, Dmitry Soshnikov wrote: On Sat, Aug 27, 2011 at 11:53 PM, John-David Dalton john.david.dal...@gmail.com wrote: No. It's the global object what is the base (more precisely, its DOM's proxy wrapper -- `window` or either the global itself), but not an

Re: double checking if window.eval(…) is an indirect call to eval().

2011-08-27 Thread John-David Dalton
@Oliver Hunt I have a vague recollection that *monkey treats global object.eval(..) as a direct eval? Firefox 4 will execute `window.eval(….)` as in the global execution context but will still allow access to variables that are accessible from the execution context of where `window.eval` was

Re: double checking if window.eval(…) is an indirect call to eval().

2011-08-27 Thread Dmitry Soshnikov
On Sun, Aug 28, 2011 at 2:06 AM, Oliver Hunt oli...@apple.com wrote: On Aug 27, 2011, at 2:42 PM, Dmitry Soshnikov wrote: On Sat, Aug 27, 2011 at 11:53 PM, John-David Dalton john.david.dal...@gmail.com wrote: No. It's the global object what is the base (more precisely, its DOM's proxy