Re: StringTokenizer class and MSVC/Win32 platform

[David Sugar]

The reason is most likely it was missed.  Yes, it should be exported.  I 
have thought about different ways of handling exports so that they don't 
interfere with other platforms which don't have this particular 
peculiarity, and never have had an entirely satisfactory answer that 
also works well with documentation generation tools.  The use of a 
__EXPORT macro in front of a class definition would mean the class was 
ignored from kdoc, for example.

The problem is if these are maintained seperately, with a seperate block 
for the exports, then one has to make sure they are all present and keep 
both in sync. Some of the newer tools will at least not crash doing 
documentation on code with such odd macros and things, so it might be 
better to put them with the defintions in the headers, at least as far 
as making sure none are missed.


Pavel Tsekov wrote:

> Hi there! :)
>
> I hope this time I'll get an answer :) 
>
> I have a program initially written on linux which uses the
> StringTokenizer class of the CommonC++ library. Now i tried to build the
> program on Win32 using MSVC and I got an error message - the linker is
> complainning that it cannot resolve the StringTokenizer and
> StringTokenizer::iterator classes... In fact they arent exporeted like
> the other classes in misc.h - look at this:
>
> #ifdef  __WIN32__
> class __EXPORT MemPager;
> class __EXPORT SharedMemPager;
> class __EXPORT Keydata;
> #endif
>
> The StringTokenizer and iterator arent included in this list - my
> question is why is this ? :)
>
> Thanks for any answers - I hope that someone will reply to this messge
> :)
>
> _______________________________________________
> Bug-commoncpp mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp