Re: [Boost-bugs] [Boost C++ Libraries] #6841: Are __cdecl and __stdcall ambiguous in CE?

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #6841: Are __cdecl and __stdcall ambiguous in CE?
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2012-05-02 13:28:40

#6841: Are __cdecl and __stdcall ambiguous in CE?
-------------------------------+--------------------------------------------
  Reporter:  viboes            |       Owner:  igaztanaga
      Type:  Bugs              |      Status:  new       
 Milestone:  To Be Determined  |   Component:  intrusive 
   Version:  Boost 1.49.0      |    Severity:  Problem   
Resolution:                    |    Keywords:  wince     
-------------------------------+--------------------------------------------
Changes (by Ulrich Eckhardt <ulrich.eckhardt@…>):

  * keywords:  => wince

Comment:

 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.

-- 
Ticket URL: <https://svn.boost.org/trac/boost/ticket/6841#comment:1>
Boost C++ Libraries <http://www.boost.org/>
Boost provides free peer-reviewed portable C++ source libraries.