Re: [Libusbx-devel] [libusbx] Windows: Avoid potential mismatch in transfer error reporting (#151)

2013-10-01 Thread Pete Batard
Makes sense. Applied. /Pete --- Reply to this email directly or view it on GitHub: https://github.com/libusbx/libusbx/pull/151#issuecomment-25500037-- October Webinars: Code for Performance Free Intel webinars can help yo

Re: [Libusbx-devel] [libusbx] Windows: Avoid potential mismatch in transfer error reporting (#151)

2013-10-01 Thread Pete Batard
Closed #151 via a9cd54f24d566062a461d27f615365f41a3d11e8. --- Reply to this email directly or view it on GitHub: https://github.com/libusbx/libusbx/pull/151-- October Webinars: Code for Performance Free Intel webinars can

[Libusbx-devel] [libusbx] Windows: Avoid potential mismatch in transfer error reporting (#151)

2013-10-01 Thread Matthias Bolte
The default case in windows_transfer_callback() calls windows_error_str(0) which will convert the error code returned by GetLastError() to a string. This currently works because windows_transfer_callback() is either called with io_result set to NO_ERROR or io_result set to GetLastError(). If windo