Fixing a subtle bug in receiver resolution when a thrown and caught function is calle...
authorolehougaard <olehougaard@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Thu, 18 Dec 2008 11:28:13 +0000 (11:28 +0000)
committerolehougaard <olehougaard@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Thu, 18 Dec 2008 11:28:13 +0000 (11:28 +0000)
commit392e6f849b6e9b63c912c4ebf6e0e5412b16a742
tree9cc3735e00744914a14d4915944f8b3994979801
parentb372ecdf95a8c9f143fd5d62f512dd30b47d6c83
Fixing a subtle bug in receiver resolution when a thrown and caught function is called from a catch-block.
Second attempt - now with better memory efficiency.
Review URL: http://codereview.chromium.org/14834

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@999 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
14 files changed:
src/ast.h
src/codegen-arm.cc
src/codegen-ia32.cc
src/contexts.h
src/factory.cc
src/factory.h
src/heap.cc
src/heap.h
src/objects-inl.h
src/objects.h
src/parser.cc
src/runtime.cc
src/runtime.h
test/mjsunit/throw-and-catch-function.js [new file with mode: 0644]