From: Orin E. <ori...@gm...> - 2011-02-28 21:49:02
|
On Mon, Feb 28, 2011 at 1:26 PM, Pete Batard <pb...@gm...> wrote: > > OK. I guess most Windows developers would be expecting a W as well, > since this is Microsoft's way to support Unicode. Right now, I'm not so > sure what we should do. I'd like to avoid having to support 2 calls just > for the Windows implementation (we're really overkilling this whole > thing IMO - it should be kept as simple as possible) but I'd like to > have something that looks familiar to Windows users... > > Would the W call be made available to POSIX users? If not, the > documentation will be quite confusing (If you're on Posix, use > strerror(). On Windows use strerrorA(), or strerrorW()). Sounds a bit > heavy for what is meant to be a simple API call... > Provide libusb_strerror() and libusb_wstrerror() on all systems. They won't be confusing to Windows programmers - after all, things like for example _tcscpy() resolve to either a standard string function (strcpy()) or a wide character function (wcscpy()). It would be wrong IMO to use the Microsoft naming convention in this case. Orin. |