Explicitly pass the closure when allocating a catch or with context.

Explicitly pass the closure when allocating a catch or with context.

Before: allocation of a catch or with context fetched the closure to store
in the context from the previous context in the context chain.  Now: the
closure is passed explicitly.

R=ager@chromium.org
BUG=
TEST=

Committed: http://code.google.com/p/v8/source/detail?r=8453

[Kevin Millikin (Chromium), 2011-06-28 17:38:44]

The old behavior assumed that the previous context had the appropriate closure.

This would not be the case, for example, if a with/catch context was nested
inside a function that didn't have its own local context.  In that case, the
previous context is some outer one with the wrong closure.

Special care has to be taken for the global scope to ensure that all such
contexts have the same empty function (to match the current behavior).  Special
care has to be taken for eval code to ensure that the anonymous closure for the
eval code doesn't show up in a context's closure field where we don't currently
expect it.

I'm not a huge fan of the complicated protocol to the runtime functions, but it
seemed simple to implement.

[Mads Ager (chromium), 2011-06-29 07:31:47]

LGTM