I've managed to narrow down a conflict between these because of the fact that Casablanca defines the "U" macro. Trying to compile a project where both headers are included will generate compile errors in the boost headers.
Using a define to ensure Casablanca does not define this causes the compile errors to go away. I'm still using 2.4, and don't really want to upgrade right now, but I figure it still applies to the latest version. This is unfortunate and really problematic since the errors generated will typically be nonsensical due to macro involvement.
I'm just reporting this in case you don't know. I'd argue that the "U" macro should be disabled by default, but of course the decision on how to use this information goes to you guys.
Thanks again for an incredibly useful library.
Using a define to ensure Casablanca does not define this causes the compile errors to go away. I'm still using 2.4, and don't really want to upgrade right now, but I figure it still applies to the latest version. This is unfortunate and really problematic since the errors generated will typically be nonsensical due to macro involvement.
I'm just reporting this in case you don't know. I'd argue that the "U" macro should be disabled by default, but of course the decision on how to use this information goes to you guys.
Thanks again for an incredibly useful library.