[Libusbx-devel] Warnings from Intel Compiler

2012-06-19 Thread Orin Eman
Since I have a copy, I compiled 1.0.12 with the Intel Compiler. I turned off the zero length array and unreferenced parameter warnings. This is what is left: Building with Intel(R) C++ Compiler 12.1 ClCompile: * ClCompile (Win32 - Intel C++) All outputs are up-to-date. core.c ..\libu

Re: [Libusbx-devel] hot unplug on windows, only 3 IN transfers complete

2012-06-19 Thread Pete Batard
On 2012.06.19 08:28, Peter Stuge wrote: > Pete Batard wrote: >> the API is really only one part of it > > In a library the API is almost the only thing that matters. Ergo, you are stating that the resources a project can muster, and users requests don't matter, as per the exact elements I was bri

Re: [Libusbx-devel] A stupid mistake

2012-06-19 Thread Jach Fong
Hi! Xiaofan, The open() function works after changing to release 1.0.12. What a stupid mistake I had made!! Thanks for help. Best Regards, Jach 2012/6/18 PM 06:14, Xiaofan Chen said: > On Mon, Jun 18, 2012 at 6:08 PM, Jach Fong wrote: >> I test it today on using the Borland C++ 5.0 (M

Re: [Libusbx-devel] hot unplug on windows, only 3 IN transfers complete

2012-06-19 Thread Peter Stuge
Pete Batard wrote: > the API is really only one part of it In a library the API is almost the only thing that matters. We've long ago established that the libusb-1.0 API doesn't fit Windows and that the Windows code has to jump through hoops because of that. > balance API requirements with resou