Hi Hal and Bob,

thanks for that info. It's a dirty workaround, and as it depends on global 
variables it will always bear the problem of potential failure in multi-
threaded programs. Additionally, as I'm coding away in Python I don't have 
those Dirty Old Tricks (TM) at hand, either.

And I believe, due to the current great overhaul and API change it would be a 
good time to introduce a more suitable concept.

Maybe all operations that could fail should return either a NULL pointer or an 
error struct, or something. That's one of the reasons I like exceptions in 
object oriented languages so much. They keep the code clean, and you can catch 
them when you feel it's fit. Not upon the function call directly. So the stack 
trace is really the tool to investigate into potential errors, too.

I'm not really too deeply rooted in the C world (just a brief working 
knowledge without expert status), but maybe someone has got a good suggestion 
to solve this problem that Marti may take up.

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

Reply via email to