Hi Richard,
Much has been discussed about this new functionality and the impact it will surely have on yet existing apps using THR functions. The main drivers I used to take the decision were: 1) Any client using THR functions and the lib as shared object is basically broken. if a client sets a listener or plug-in, it got events from any other clients of the .so, with obviously unexpected user data format. This causes segfaults. 2) Anybody using the library as static can use the flag to revert to old behavior. Otherwise the compiler issues a warning on places where things have changed. 3) Some cases (small integers, pointers to structures) are detected automatically. Those cases were NOT WORKING previously because rule 1) and now are fixed. So basically this is breaking the ABI compatibility, but the cases where ABI is broken were not working anyway. So hence the decision of fixing the whole thing at the expense of ABI compatibility. I agree a .soname bump should be required here. I can even do a major version bump to lcms2-3.0, your feedback would be appreciated. Regards Marti ------------------------------------------------------------------------------ Android apps run on BlackBerry 10 Introducing the new BlackBerry 10.2.1 Runtime for Android apps. Now with support for Jelly Bean, Bluetooth, Mapview and more. Get your Android app in front of a whole new audience. Start now. http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk _______________________________________________ Lcms-user mailing list Lcms-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lcms-user
