> The callback signature changes alone break almost every single line of > v8-using code i've written (tens of thousands of them), and i am still > undecided as to whether to spend several weeks of my time patching for or > whether to simply drop by v8-related projects (i'm leaning strongly towards > the latter). i'm getting too old to spend weeks patching every time a > 3rd-party library pulls the rug out from under me (and this isn't the first > time v8 has done it, though this is certainly the most invasive change so > far). > I feel your pain. Converting chrome was a large amount of tedious work.
Ultimately, though, the v8 team does not want to support two APIs for any sustained amount of time. I've put up a header only library on github that embedders can use if they do not want to rewrite all their callbacks: https://github.com/drcarney66/v8-backport. You will, however, have to install wrap<your_old_function_name> at callback registration time instead of your_old_function_name. This far from a perfect solution, but should help in a lot of cases, and it's certainly less work that manually converting a zillion functions. Note that performance sensitive functions should be converted. Additionally, as things like Arguments, InvocationCallback, and AccessorInfo are removed from v8.h, I'll just create a compatible version in the header which should keep things compiling for anyone choosing to use that library. One further note: instead of removing Local, Handle is going to be removed instead, which should cause embedders a lot less pain. -- -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" 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.
