Re: problems with callback function
Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance
> It appears to me that your project's calling convention is set to
> something other than _cdecl. Perhaps you have it set to _stdcall?
no, for the file in question the calling convention is set to _cdecl.
Mark
.
Relevant Pages
- Re: problems with callback function
... >> It appears to me that your project's calling convention is set to something other than _cdecl. ... >> Perhaps you have it set to _stdcall? ... Prev by Date: ...
(microsoft.public.vc.language) - Mixed stdcall and cdecl code
... I'm writing a DirectShow capture filter, which requires the stdcall calling ... cdecl calling convention, because I was getting "unresolved external symbol" ... or am I likely to have stack problems unless I explicitly declare ...
(microsoft.public.win32.programmer.directx.video) - Mixed stdcall and cdecl code
... I'm writing a DirectShow capture filter, which requires the stdcall calling ... cdecl calling convention, because I was getting "unresolved external symbol" ... or am I likely to have stack problems unless I explicitly declare ...
(microsoft.public.multimedia.directx.dshow.programming) - Re: calling convention stdcalll and cdecl call
... The standard calling convention dates back to 16 bit ... || variable-length argument lists. ... but does not allow for variable-length argument ... The __cdecl calling convention creates larger ...
(microsoft.public.vc.language) - Re: calling convention stdcalll and cdecl call
... The only reason stdcall was ... But you are correct of course and the reason ... The standard calling convention dates back to 16 bit ... The __cdecl calling convention creates larger ...
(microsoft.public.vc.language) |
|
