On Mon, 2012-06-04 at 14:03 -0700, Jeremy Huddleston wrote: > On Jun 4, 2012, at 1:34 PM, Julien Cristau <jcris...@debian.org> wrote: > > How are the xcb_atom_get_predefined/xcb_atom_get_name_predefined > > removals not binary incompatible?? > > Nothing else changed, just the removal of the symbols. All other > functions did not change their signatures.
That's irrelevant. > Think about this from the libc perspective. libc *may have* strlcat > or not, but they're named the same because all functions in libc have > consistent signatures. A libc that had strlcat once, and then removed it, would no longer have the same ABI. An application that had successfully linked against the old libc's strlcat would reasonably expect it to be present at runtime too. Removal of exported functions is an ABI break, even in Mach-O. The soname (or dylib mahor version number) _should_ change. - ajax
signature.asc
Description: This is a digitally signed message part
_______________________________________________ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
