Hi, I'm playing a bit with the preview of lcms 2.0 right now (more particularly with ctypes based Python bindings). I've seen in the code that the error handler again is just a callback function that is globally set.
I'd appreciate it if some mechanism for error handling/reporting could be found that is more robust towards e. g. concurrent systems. Especially as lcms is now being used in many larger applications as well, having particularly Mozilla in mind. How is a calling code supposed to find out if an error with lcms has happened, if some global/remote call back is called. The code itself cannot handle that situation locally with the mechanism in place in lcms 1.x and as well the current preview of 2.0. Especially stack traces in the error handler function assigned are also quite pointless as it's very hard to trace back the origin of some error within the code. Any other opinions? Guy -- Guy K. Kloss Institute of Information and Mathematical Sciences Te Kura Pūtaiao o Mōhiohio me Pāngarau Room 2.63, Quad Block A Building Massey University, Auckland, Albany Private Bag 102 904, North Shore Mail Centre voice: +64 9 414-0800 ext. 9585 fax: +64 9 441-8181 eMail: g.kl...@massey.ac.nz http://iims.massey.ac.nz ------------------------------------------------------------------------------ SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. The future of the web can't happen without you. Join us at MIX09 to help pave the way to the Next Web now. Learn more and register at http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/ _______________________________________________ Lcms-user mailing list Lcms-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lcms-user
