Am 13.02.2014 23:05, schrieb Graeme Gill: > marti.ma...@littlecms.com wrote: > >> Yep, that is how actually works, and this is the source of all pain. >> What I really need is a sort function that given a pointer, would guess >> if this points to a cmsContext internal structure or to used supplied >> data. > If the client code has to be changed anyway to use the new cmsContext > (ie. to get one and then supply it to each function call), then another > approach would be to use different function names for the cmsContext, > ie. cmsCreate_sRGBProfileLCX() etc., so that the _THR functions > can remain unchanged, and internally there is then no doubt > about what sort of context it is.
1+ Escaping the incompatible APIs appears to me as the best suggestion so far. _THR functions can be deprecated and a new function set can be introduced at the same release. THR would be removed on the next major. The changes on user side would not involve more work on making them ready for the new APIs. But it would satisfy old code demands, which makes sense to many users. kind regards Kai-Uwe ------------------------------------------------------------------------------ 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
