Boost C++ Libraries: Ticket #6841: Are cdecl and stdcall ambiguous in CE?

keywords set

Wed, 02 May 2012 13:28:40 GMT

keywords wince added

If you peek around the Windows CE headers, you will find that one is #defined to the other. I remember that you can use those before the according headers are included, which can mess things up if you have code like this (from the top of my head, not actually compiled):

    int __cdecl foo();
    #include <windows.h>
    int __cdecl foo()
    { return 42; }

BTW: I see that you are currently trying to take care of the CE port. If you add the "wince" keyword, all those tickets are easier to find. I also need a CE port, but I'm currently swamped with other work, so at best I can watch what's going on and try to help out.

David Deakins — Thu, 10 May 2012 03:45:10 GMT

I actually had a little bit of time to look at this and built the attached simple patch for mpl.hpp. After applying it, nearly all of the intrusive tests seem pass without issue on WinCE.

attachment set

David Deakins — Thu, 10 May 2012 03:46:23 GMT

attachment → boost-intrusive-mpl.hpp.patch

patch to adjust mpl.hpp

status changed; resolution set

Ion Gaztañaga — Thu, 12 Jul 2012 07:31:12 GMT

status new → closed
resolution → fixed

Fixed at revision 78474 in trunk

Boost C++ Libraries: Ticket #6841: Are __cdecl and __stdcall ambiguous in CE?

keywords set

attachment set

status changed; resolution set

Boost C++ Libraries: Ticket #6841: Are cdecl and stdcall ambiguous in CE?