When I read the documentation, I thought that the only difference between the
libusb_get_string_descriptor and _ascii function was that the former returned
UTF-16. I was surprised when I discovered that it was actually such a thin
wrapper.
The documentation says:
> number of bytes returned in data, or LIBUSB_ERROR code on failure
In my opinion in makes perfectly sense for the API to return an error when the
format does not conform to the USB standard.
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/pull/156#issuecomment-27718664
------------------------------------------------------------------------------
Android is increasing in popularity, but the open development platform that
developers love is also attractive to malware creators. Download this white
paper to learn more about secure code signing practices that can help keep
Android apps secure.
http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk
_______________________________________________
libusbx-devel mailing list
libusbx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libusbx-devel
