warning C4441: calling convention of '__stdcall ' ignored; '__clrcall ' used instead

warning C4441: calling convention of '__stdcall ' ignored; '__clrcall ' used instead

• ZAP2944

  If you had read my post you will have read that I stated where CB_Callback is used to decorate a function I get the C4441 warning; I make no statements about #define causing the problem.

  Thank you for the help but give it to someone else -- life is too short to be listening to your sarcasm.

  Direct from my code ...

  // Calling convention for callbacks

  #if defined(WIN32) || defined(WIN64)

  #define CB_Callback __stdcall

  #else

  #define CB_Callback

  #endif

  void* CB_Callback CB_Callback_DoAlloc(unsigned long nSize, const void *pParam);

  warning C4441: calling convention of '__stdcall ' ignored; '__clrcall ' used instead

  
  

• BactBob

  That is the direction I am going to try -- the difficulty is that within the body of my callback I have to reference objects in managed code. I wish there was an easier way to do this.
  

• Rvel

  Nishant Sivakumar wrote:

  Managed types need to use __clrcall. The only way to avoid the warning is to change the code or to put those functions in a non-CLI type.

  It is a third party static lib so I don't have the luxory of just changing it.

  
  

• ggssu

  As mentioned this is a third party static Lib so I have no control in making changes.

  I am also going to be calling a Win32 API that I believe also uses __stdcall so I will be running into the problem there as well.

  I am very surprised there is no means of using existing libraries that have a __stdcall calling convention.

  nobugz wrote:

  The code that generates the warning jumps to mind. As well as the declaration of the callback function in the .lib

  
  

• KitWest

  Nishant Sivakumar wrote:

  The warnings are thrown on code in your managed project. Could you copy/paste those lines here please

  I have a header file include that contains

  // Calling convention for callbacks

  #if defined(WIN32) || defined(WIN64)

  #define CB_Callback __stdcall

  #else

  #define CB_Callback

  #endif

  Then in my code whereever there is use of CB_CallBack I get the following warning:

  Output is:

  : warning C4441: calling convention of '__stdcall ' ignored; '__clrcall ' used instead

  
  

• Fatou

  Managed types need to use __clrcall. The only way to avoid the warning is to change the code or to put those functions in a non-CLI type.
  
  

• Joleen

  >> Then in my code whereever there is use of CB_CallBack I get the following warning: <<

  Are you using CB_CallBack on methods of CLI types If so, that's not possible. You can use unmanaged types in a /clr project. Declare your callback functions as methods of the unmanaged class - and use that to interface with the methods in the statically linked library.

  
  
  

• Dirty Steve

  Look three messages above -- wherever CB_Callback is used to decorate a function I get the C4441 -- no baloons.
  

• TA_R_EK

  Sorry to get a bit cranky here but we're 9 posts into this thread, it is already marked as answered but I still haven't seen the line of code that generates the warning. Is it real or just a balloon
  
  
  
  

• Marc Tomlinson

  The code that generates the warning jumps to mind. As well as the declaration of the callback function in the .lib
  
  
  

• Brandon K

  You are getting a warning on a #define That's a really kewl compiler you're using. Good luck BS-ing somebody else...
  
  
  
  

• Shirvo

  This doesn't sound good. When functions are compiled with the /clr option in effect, the compiler normally generates two entrypoints for a function, native and CLI. That probably didn't happen for the code in the static library, it just has a native entrypoint. The warning suggests it wants to call the CLI entrypoint. I'd expect it to go kaboom when it does. Show us the relevant code snippets to diagnose this.
  
  
  
  

• Stitchy

  There isn't any code to show -- these are just functions in a static lib that are native Win32 with calling convention __stdcall.

  So how do you mix managed and unmanaged code Isn't there a way of leveraging existing libraries

  nobugz wrote:

  This doesn't sound good. When functions are compiled with the /clr option in effect, the compiler normally generates two entrypoints for a function, native and CLI. That probably didn't happen for the code in the static library, it just has a native entrypoint. The warning suggests it wants to call the CLI entrypoint. I'd expect it to go kaboom when it does. Show us the relevant code snippets to diagnose this.

  
  

• Manuel Basurto

  The warnings are thrown on code in your managed project. Could you copy/paste those lines here please
  
  
• warning C4441: calling convention of '__stdcall ' ignored; '__clrcall ' used instead