
25 May
2006
25 May
'06
5:14 a.m.
David Abrahams wrote:
David Abrahams <dave@boost-consulting.com> writes:
There is also at least one macro in that category: BOOST_EXPORT. That in particular seems likely to cause problems, because after all "export" is a keyword that's supported only on a few compilers and a natural stand-in, for those who want to support export, would be BOOST_EXPORT. This should've been BOOST_SERIALIZATION_EXPORT.
BOOST_DLLEXPORT, BOOST_USED, ...
If that macro does what I think it does BOOST_DLLEXPORT is a bad choice. DLL exporting macros *must* be library specific otherwise boost libraries can not use each other. For an example look at the AFX_DLL mess MS created. Thomas -- Thomas Witt witt@acm.org