exposing some methods from objects.h (alternative to counters)

src/runtime.h

Index: src/runtime.h
diff --git a/src/runtime.h b/src/runtime.h
index 5efc057df9da2b1b897b7242c2a56810e2afcdef..108c965d9566a766af3d04ad9e3460bf060d3ea1 100644
--- a/src/runtime.h
+++ b/src/runtime.h
@@ -334,7 +334,23 @@ namespace internal {
   F(MessageGetScript, 1, 1) \
   \
   /* Pseudo functions - handled as macros by parser */ \
-  F(IS_VAR, 1, 1)
+  F(IS_VAR, 1, 1) \
+  \
+  /* expose boolean functions from objects-inl.h */ \
+  F(ObjectHasFastElements, 1, 1) \

[danno, 2011/06/30 17:24:04]

Is there any reason that you don't call these HasXXX rather than ObjectHasXXX?
Names without the Object prefix are more consistent with other functions like
HasProperty or HasElement.

+  F(ObjectHasFastDoubleElements, 1, 1) \
+  F(ObjectHasDictionaryElements, 1, 1) \
+  F(ObjectHasExternalPixelElements, 1, 1) \
+  F(ObjectHasExternalArrayElements, 1, 1) \
+  F(ObjectHasExternalByteElements, 1, 1) \
+  F(ObjectHasExternalUnsignedByteElements, 1, 1) \
+  F(ObjectHasExternalShortElements, 1, 1) \
+  F(ObjectHasExternalUnsignedShortElements, 1, 1) \
+  F(ObjectHasExternalIntElements, 1, 1) \
+  F(ObjectHasExternalUnsignedIntElements, 1, 1) \
+  F(ObjectHasExternalFloatElements, 1, 1) \
+  F(ObjectHasExternalDoubleElements, 1, 1)
+
 
 #ifdef ENABLE_DEBUGGER_SUPPORT
 #define RUNTIME_FUNCTION_LIST_DEBUGGER_SUPPORT(F) \