2010/4/8 Xiaofan Chen <xiaof...@gmail.com>: > On Thu, Apr 8, 2010 at 10:01 PM, Xiaofan Chen <xiaof...@gmail.com> wrote: >> Ah, this may be the case. I need to ask again in the libusb mailing >> list. The MSVC solution generates stdcall. And I believe if they >> are different, then Pete will need to change the MinGW/Cygwin >> build to use stdcall. >> > > Indeed this is a problem. > http://old.nabble.com/Calling-convention-of-the-libusb-1.0-Windows-snapshots-td28179386.html > > In my opinion, both should match and it seems to me using > stdcall is the way to go. > > Wander: what is your opinion as the pyusb developer?
As a library developer, I understand that calling convention is part of the API interface, and it should be explicit in the header file. If we are speaking on Windows, and we want to support as much clients as possible, we should we __stdcall. Some environments just cannot handle __cdecl (coff coff VB6). > > > -- > Xiaofan http://mcuee.blogspot.com > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > pyusb-users mailing list > pyusb-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/pyusb-users > ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ pyusb-users mailing list pyusb-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pyusb-users
