In general, you need to recompile your app for each new V8 version. We do not provide a stable ABI.
-- Mads On Thu, Dec 10, 2009 at 3:02 AM, Abdulla Kamar <[email protected]> wrote: > So I wouldn't be able to assume that a patch level change (the patch in > major.minor.patch) would make no changes to the ABI or API? > > On Thu, Dec 10, 2009 at 12:50 PM, Jens Alfke <[email protected]> wrote: >> >> On Dec 9, 2009, at 5:37 PM, Abdulla wrote: >> >> > I was wondering if there are any ABI/API guarantees between between >> > versions? Does a major release break the ABI? Does a minor release >> > only add to the ABI/change API? Does a patch level only signify a bug >> > fix? >> >> I am not on the V8 team, but: >> >> The V8 API (v8.h) is object-based C++. It is infamously hard to preserve >> binary compatibility in a C++ API — the only projects I know of that have >> seriously attempted to do it (BeOS and Apple's IOKit) had to restrict >> themselves to a small subset of C++ and pay careful attention to things like >> vtable sizes and offsets. >> >> So I would guess that the answer is no, there is no stable ABI for v8. >> You'd need to statically link a copy of v8 into your client app, or at least >> tightly rev-lock the shared library to your client code so they can't get >> out of sync. >> >> —Jens >> >> -- >> v8-users mailing list >> [email protected] >> http://groups.google.com/group/v8-users > > > -- > Thank you > Abdulla > > -- > v8-users mailing list > [email protected] > http://groups.google.com/group/v8-users -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users
