- 31 Oct, 2011 1 commit
-
-
lrn@chromium.org authored
Previously we omitted all cases where the global eval property was shadowed, even if by a variable holding the same value. ES5 requires us to treat these as direct calls. We still throw if calling indirect eval with a detached global object. BUG=v8:994 TEST=mjsunit/eval.js Review URL: http://codereview.chromium.org/8343054 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@9838 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 28 Apr, 2011 1 commit
-
-
kmillikin@chromium.org authored
The corner case is calling a function named 'eval' that is looked up at runtime and found in a non-global context (but not an extension object). The bug is that we used the function itself as the receiver rather than using the global object. R=ager@chromium.org TEST=has been added to the eval mjsunit test Review URL: http://codereview.chromium.org/6893057 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@7696 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 04 Jun, 2010 1 commit
-
-
ager@chromium.org authored
perform a context lookup in the runtime system for the 'eval' function. Instead load the 'eval' function from the global context in generated code if it is not shadowed. Will port to other platforms as a separate change. Review URL: http://codereview.chromium.org/2666001 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@4794 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 05 Jan, 2010 1 commit
-
-
kasperl@chromium.org authored
stack traversal code. Review URL: http://codereview.chromium.org/523051 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@3533 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 27 Nov, 2008 1 commit
-
-
olehougaard authored
Review URL: http://codereview.chromium.org/12673 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@860 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-