https://codereview.chromium.org/238803002/diff/20001/include/v8-debug.h
File include/v8-debug.h (left):
https://codereview.chromium.org/238803002/diff/20001/include/v8-debug.h#oldcode195
include/v8-debug.h:195: static void DebugBreak(Isolate* isolate = NULL);
On 2014/04/17 14:24:07, Paweł Hajdan Jr. wrote:
Shouldn't these also go through V8_DEPRECATED before
backwards-incompatible
removal of the default parameter?
In theory yes, in practice no. The current changes done by me and Jochen
on the API are more than superficial API changes, we are changing the
semantics of the API (in this case: nuke the default Isolate). Keeping
the old semantics without a default Isolate is not possible, so things
are just removed.
As a general rule of thumb, we try to follow a deprecation "process",
but sometimes it's just impossible or would be too much of a burden. API
stability is a non-goal for Chrome, and it is a non-goal for V8.
https://codereview.chromium.org/238803002/
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
