This one time, at band camp, Junichi Uekawa wrote: ># If anyone has a good tool, please tell me.
Well, I'm thinking of a way to automate these checks, hence my question. So, as I understand it, there's an _incompatible_ API change (and thus requiring a SONAME change) when: * function prototypes (incl names) that are exported are changed or obsoleted * structs change or are obsoleted I think I can see a way to check for both cases, given the old and new library and header file... I'll keep you posted. -- [EMAIL PROTECTED] http://spacepants.org/jaq.gpg Too many clicks spoil the browse.
