Hi Marti, Kai-Uwe, Hans and others,
To come around this problem I've added a #define in the lcms header that's part of a dirty patch I included in the new xcalib version:
I obviously see your point. And agree BOOL and in general all windows-like types would pollute global namespace. My main concern
is about breaking existing code. Let's take for example the tifficc utility.
It just #includes the lcms header and then use BOOL, DWORD and so
in the rest of program.
http://www.etg.e-technik.uni-erlangen.de/web/doe/xcalib/xcalib-source-0.4.tar.gz
It's basically working by setting -DBOOL_CONFLICT or whatever conflicts. This wouldn't break existing code and delay a forced version bump.
Stefan
------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ Lcms-user mailing list Lcms-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lcms-user
