On 2012.05.08 12:16, Ludovic Rousseau wrote: > I get these compiler warnings: > > sync.c: In function ‘libusb_control_transfer’: > sync.c:122: warning: enumeration value ‘LIBUSB_TRANSFER_ERROR’ not > handled in switch > sync.c:122: warning: enumeration value ‘LIBUSB_TRANSFER_CANCELLED’ not > handled in switch
On which platform did you get those, and with which compiler? > Maybe the LIBUSB_TRANSFER_ERROR and LIBUSB_TRANSFER_CANCELLED are > correctly handled by the default case. Maybe a more appropriate (or > more explicit) error message than LIBUSB_ERROR_OTHER can be used > instead. Well, the "unrecognised status code" message doesn't seem too accurate for errors we actually know the code of, so at least the message should go. I'd go for simply returning LIBUSB_ERROR_IO, rather than LIBUSB_ERROR_OTHER for these codes. Regards, /Pete ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ libusbx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libusbx-devel
