From: Jeff Idol (jeffidolh_at_[hidden])
Date: 2006-07-05 16:18:38
Sorry it took me so long to get back with everyone, I am getting married so I have been a little busy. The following functions are causing compile errors in STDCALL.
Also, what rewrite work is going on with the thread library?
Anthony Williams <anthony_at_[hidden]> wrote: Jeff Idol 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
-- Anthony Williams Software Developer Just Software Solutions Ltd http://www.justsoftwaresolutions.co.uk _______________________________________________ threads-devel mailing list threads-devel_at_[hidden] http://lists.boost.org/mailman/listinfo.cgi/threads-devel --------------------------------- Sneak preview the all-new Yahoo.com. It's not radically different. Just radically better.