kmillikin@chromium.org f4c4df2d9a Introduce scopes to keep track of catch blocks at compile time. ... The catch variable is bound in the catch scope. For simplicity in this initial implementation, it is always allocated even if unused and always allocated to a catch context even if it doesn't escape. The presence of catch is no longer treated as a with. In this change, care must be taken to distinguish between the scope where a var declaration is hoisted to and the scope where the initialization occurs. R=ager@chromium.org BUG= TEST= Review URL: http://codereview.chromium.org/7280012 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@8496 ce2b1a6d-e550-0410-aec6-3dcde31c8c00		2011-06-30 14:37:55 +00:00
..
benchmarks	Change cctests to use variant flags as part of the name for the serilization file.	2011-03-21 12:57:25 +00:00
cctest	Fix build on x64	2011-06-29 14:28:41 +00:00
es5conform	Reapply 7763, including arm and x64 variants.	2011-05-05 05:21:30 +00:00
message	Change cctests to use variant flags as part of the name for the serilization file.	2011-03-21 12:57:25 +00:00
mjsunit	Introduce scopes to keep track of catch blocks at compile time.	2011-06-30 14:37:55 +00:00
mozilla	Updated test expectations of future reserved keyword tests.	2011-06-24 16:54:47 +00:00
preparser	Proper handling of future reserved words in strict and normal mode.	2011-06-24 14:59:51 +00:00
sputnik	Do not pass the global object as the receiver to strict-mode and	2011-06-30 12:29:19 +00:00
test262	Bring test262 expectations up-to-date.	2011-04-11 13:54:30 +00:00