Author: [email protected]
Date: Tue Mar 24 04:07:09 2009
New Revision: 1592

Modified:
    branches/bleeding_edge/ChangeLog
    branches/bleeding_edge/src/api.cc

Log:
Preparing push of version 1.1.2 to trunk.
Review URL: http://codereview.chromium.org/42556

Modified: branches/bleeding_edge/ChangeLog
==============================================================================
--- branches/bleeding_edge/ChangeLog    (original)
+++ branches/bleeding_edge/ChangeLog    Tue Mar 24 04:07:09 2009
@@ -1,3 +1,30 @@
+2009-03-24: Version 1.1.2
+
+        Improved frame merge code generated by the code generator.
+
+        Optimized String.prototype.replace.
+
+        Implemented __defineGetter__ and __defineSetter__ for properties
+        with integer keys on non-array objects.
+
+        Improved debugger and profiler support.
+
+        Fixed a number of portability issues to allow compilation for
+        smaller ARM devices.
+
+        Exposed object cloning through the API.
+
+        Implemented hidden properties.  This is used to expose an identity
+        hash for objects through the API.
+
+        Implemented restarting of regular expressions if their input
+        string changes representation during preemption.
+
+        Fixed a code generator bug that could cause assignments in loops
+        to be ignored if using continue to break out of the loop (issue
+        284).
+
+
  2009-03-12: Version 1.1.1

          Fixed an assertion in the new compiler to take stack overflow

Modified: branches/bleeding_edge/src/api.cc
==============================================================================
--- branches/bleeding_edge/src/api.cc   (original)
+++ branches/bleeding_edge/src/api.cc   Tue Mar 24 04:07:09 2009
@@ -2273,7 +2273,7 @@


  const char* v8::V8::GetVersion() {
-  return "1.1.2 (candidate)";
+  return "1.1.3 (candidate)";
  }



--~--~---------~--~----~------------~-------~--~----~
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
-~----------~----~----~----~------~----~------~--~---

Reply via email to