Each separate library must have its own QPID_*_EXTERN macro.
Publically usable classes should either be marked or the methods
inside them. For the most part we've marked methods to avoid problems
with ancestor classes.
+1. Its a must that we should have QPID_*_EXTERN for each library
Hi Steve,
Is there a guideline for the usage of __declspec for Windows builds? I
see that you have put them on most, but not all, public methods in the
C++ APIs. I'm working on some updated APIs for management and I'd like
to save you the trouble of having to edit the headers.
Thanks,
Hi Ted,
Is there a guideline for the usage of __declspec for Windows
builds?
Each separate library must have its own QPID_*_EXTERN macro.
Publically usable classes should either be marked or the methods
inside them. For the most part we've marked methods to avoid problems
with ancestor
