Thanks, that's an interesting report. I think that these are all harmless, though. Most are cases of new API calls being added. In one case, a parameter was renamed (truly of no consequence), and in two cases a default argument was turned into no longer a default.
In all cases, old apps that switch to link against the new library should be fine without recompilation. It's possible, in the case of the changing default argument, that if you recompile the app source and you happened to rely on that default argument, you'll need to patch it to pass the argument. This change was not intentional. But I'm pretty sure it happened several releases ago, not in the latest couple updates, so I'm tempted to not worry about it unless you think it's important to change it again to restore the default. I'll be more careful in the future about not changing default parameter values in release branches, I didn't really mean to do that. On Apr 23, 2013, at 6:43 AM, Richard Shaw wrote: > Looks ok to me but there are a few compatibility warnings. You may be > interested in a abi comparison. The only other abi dump I had handy in 1.1.X > was 1.1.3: > > https://dl.dropboxusercontent.com/u/34775202/compat_reports/OpenImageIO/1.1.3_to_1.1.10/compat_report.html > > Richard > _______________________________________________ > Oiio-dev mailing list > [email protected] > http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org -- Larry Gritz [email protected]
_______________________________________________ Oiio-dev mailing list [email protected] http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
