How to deal with OTK 'optional' conflicting with C++11 std::optional

FV wrote: OTK defines 'optional' in ciptype.h with the simple '#define optional' statement. Why anybody would use preprocessor definitions in C++ API made for public consumption is beyond comprehension... Anything based on std::optional (or boost::optional) causes compilation errors Hi Feliks - I, too, have been burned by '#define optional' in OTK C++. It caused a tangle of compiler errors with Boost Geometry, which depends on boost::optional. I was able to mitigate the issue somewhat by changing the order of my #include statements, but I ultimately resolved the problem by removing most of the OTK C++ code from that project. This problem will only get worse when std::optional is officially incorporated as expected in the C++17 standard. I believe that the OTK C++ library overuses C preprocessor macros. The try/xcatchbegin/xcatch/xcatchend syntax is another example. In the case of '#define optional', it was bad judgement on PTC's part to use a common English word, in all lowercase, as the name of a preprocessor macro.  Any good book on C will tell you to name these macros in all uppercase and to use a distinctive naming pattern, like "#define OTKCPP_OPTIONAL ...". Any good book on C++ will tell you to use preprocessor macros only as a last resort. Back to addressing this problem: Have you tried changing the order of you #include statements? Also, can you use '#undef optional' to mitigate this problem? |+|  M a r k  |+|