On 2013/12/18 06:57:18, Sven Panne wrote:
Thinking about this CL a bit more: As was already mentioned, we plan to
remove
all deprecated API entries now plus even a handful of things which were
not
deprecated. The rationale behind this is that we really, really need to
clean
up
our Isolate story, and these entries are road blocks for this. Although we
have
a (sloppy) policy to deprecate things for 1 release before they vanish, we
think
that one big cleanup/removal is easier to communicate than a constantly
moving
API in the foreseeable future, at least if you don't break the policy to
often.
Let's have an API without any deprecations for the next release.
What this means for this CL is that I would prefer to remove the API
entries
instead of marking them deprecated. If needed, change Chrome first.
Chromium side is already prepared for this so I don't mind removing all
these
methods without deprecating them first. It sounds a bit weird that we have
an
exception to the regular deprecation policy in this case though. Of cause
it is
always easier to delete deprecated methods immediately as soon as Chromium
is
prepared for this but other embedders may be not be happy with that.
https://codereview.chromium.org/117353002/
--
--
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/groups/opt_out.
