|
|
Threads-Devel : |
From: Anthony Williams (anthony_at_[hidden])
Date: 2006-06-12 15:26:51
Jeff Idol <jeffidolh_at_[hidden]> writes:
> I recently changed my boost install to build everything in STDCALL by
> changing the compile flags. This worked well for all of the other libraries
> except for python and thread.
>
> I did some quick checking, and it appears that there are some windows
> specific C functions in thread that are required to be compiled CDECL
> because of windows thread function syntax. While most of the functions have
> been correctly prototyped and defined, there seem to be several that are
> still not setup properly. I have been able to compile them by just
> explicitly putting the proper CDECL statements in the functions.
>
> So my question really is, has anyone else noticed this issue, and are there
> any plans to fix it?
I haven't noticed, but I don't tend to change the default calling
convention. The thread-related functions that require CDECL should be declared
as such, for precisely this reason --- the calling convention of C++ functions
is not specified. If you can list the functions that are causing you problems,
we can look into this, and ensure that this problem doesn't occur with the
rewrite.
Anthony
-- Anthony Williams Software Developer Just Software Solutions Ltd http://www.justsoftwaresolutions.co.uk