I would support this change, too, for various reasons. In the past, the
external
API changed only very slowly, so it was easy for embedders to follow.
Recently,
the rate of change went up dramatically, so the embedder's life got much
harder.
The external API will hopefully stabilize in the next few weeks/months, but
making transitions easier and making v8 a good team player in the Open
Source
sense wouldn't hurt, anyway.
Another reason for this change is that it would make upgrading v8 in our
internal projects easier and less of a Herculean effort: With the version
macros
in place, one could tentatively prepare embedding projects *before*
updating v8,
and one could easily revert to the previous version when things go wrong.
This
advantage alone should be enough to warrant this change.
In a nutshell: A strong +1 for this CL from my side.
https://codereview.chromium.org/23723003/
--
--
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.
