Remove ConfigureDefaults version that does not take the amount of virtual mem

include/v8.h

Index: include/v8.h
diff --git a/include/v8.h b/include/v8.h
index 9d43cd7cfe8ed0feab6a33d4d484408f2c690bc7..e0254ff598e2870ab16b9954f8730f3eadf0ca81 100644
--- a/include/v8.h
+++ b/include/v8.h
@@ -3959,11 +3959,6 @@ class V8_EXPORT ResourceConstraints {
   void ConfigureDefaults(uint64_t physical_memory,
                          uint64_t virtual_memory_limit,
                          uint32_t number_of_processors);
-  // Deprecated.

[Paweł Hajdan Jr., 2014/04/17 14:16:24]

Wait, this did not get through V8_DEPRECATED process. Is that really OK?

[jochen (gone - plz use gerrit), 2014/04/17 14:20:31]

There is no such process.

[Paweł Hajdan Jr., 2014/04/28 12:21:11]

I'm surprised by this, could you explain more?

I can understand starting with just a // Deprecated comment as opposed to
V8_DEPRECATED so that Chromium can compile.

But then it seems the course of action would be to use V8_DEPRECATED rather than
removing the API immediately.

-  void ConfigureDefaults(uint64_t physical_memory,
-                         uint32_t number_of_processors) {
-    ConfigureDefaults(physical_memory, 0, number_of_processors);
-  }
 
   int max_young_space_size() const { return max_young_space_size_; }
   void set_max_young_space_size(int value) { max_young_space_size_ = value; }