[Isolates] Avoid isolate lookup in HandleScope destructor.

include/v8.h

Index: include/v8.h
diff --git a/include/v8.h b/include/v8.h
index e05bf8ee8c3ef21fbba1fa028dce73b1b24c90f2..e6508b7407603210ef654eed2173e19422d69515 100644
--- a/include/v8.h
+++ b/include/v8.h
@@ -470,9 +470,11 @@ class V8EXPORT HandleScope {
     int extensions;
     internal::Object** next;
     internal::Object** limit;
-    inline void Initialize() {
+    internal::Isolate* isolate;
+    inline void Initialize(internal::Isolate* i) {

[Dmitry Titov, 2010/09/29 22:14:47]

Tiny nit, to consider, but I'm 50-50 on it myself:

It feels that Initialize is used more like "Reset" (at least in api.cc).

If the Data had a constructor taking Isolate*, then we could remove call to
Initialize from isolate.cc and don't do change in api.cc.

[Vitaly Repeshko, 2010/10/01 17:16:49]

When Data is used in an API HandleScope it can't be constructed with the right
arguments and stays uninitialized for a while. So it's more natural to
initialize it than to reset.

       extensions = -1;
       next = limit = NULL;
+      isolate = i;
     }
   };