http://codereview.chromium.org/100158/diff/1/3 File include/v8-debug.h (right):
http://codereview.chromium.org/100158/diff/1/3#newcode205 Line 205: static void SetMessageHandler2(MessageHandler2 handler); On 2009/04/29 12:36:08, Yury Semikhatsky wrote: > When all clients are switched to the new message handler we will need to remove > the old one and rename SetMessageHandler2 to SetMessageHandler which will break > the code anyway. Consider switching to the new API without this intermediate > step. I agree that this is not optimal, but we need to keep the Webkit (V8-Latest) builder happy so that we can catch any regressions before pushing to trunk. This API incompatibility is actually such a regression. When we push to trunk with the rename from MessageHandler2 -> MessageHandler the DEPS roll and the client changes in Chromium can be done as a single commit. http://codereview.chromium.org/100158 --~--~---------~--~----~------------~-------~--~----~ v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev -~----------~----~----~----~------~----~------~--~---
