You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm working on some regression tests in C++ for a plugin I'm writing, and have just found my build failing in Linux (though not OS X, for some reason). The error message led me to the discovery that in avxplugin.h, the block of macros including assert.h and crtdbg.h is located within the 'avxsynth' namespace. The unit testing framework I'm using (Catch) also needs assert.h, but it can't find the names it's looking for since the header's already been included under your namespace.
Moving the aforementioned block of macros up out of the namespace fixes the issue for me. I can also work around this by either including catch.hpp before avxplugin.h, or by adding 'using namespace avxsynth' after including your header but before the test framework, but both of those approaches seem fragile to me. Am I right in believing the includes should be pulled out of the namespace, or is your placement of that code by design?
The text was updated successfully, but these errors were encountered:
I'm working on some regression tests in C++ for a plugin I'm writing, and have just found my build failing in Linux (though not OS X, for some reason). The error message led me to the discovery that in avxplugin.h, the block of macros including assert.h and crtdbg.h is located within the 'avxsynth' namespace. The unit testing framework I'm using (Catch) also needs assert.h, but it can't find the names it's looking for since the header's already been included under your namespace.
Moving the aforementioned block of macros up out of the namespace fixes the issue for me. I can also work around this by either including catch.hpp before avxplugin.h, or by adding 'using namespace avxsynth' after including your header but before the test framework, but both of those approaches seem fragile to me. Am I right in believing the includes should be pulled out of the namespace, or is your placement of that code by design?
The text was updated successfully, but these errors were encountered: