2012/9/15 Pete Batard <p...@akeo.ie>: > I have now pushed the bMaxPower change to mainline. Before I go 1.0.13-rc1 > however, I think I'm warming up to the idea of having a macro in libusb.h, > that could be used to uniquely identify API changes. > > Basically, I'm thinking of something like: > > #define LIBUSBX_API_VERSION 0x01001234
No objection. > Otherwise, for the bMaxPower update, my current preferred proposal would be > to have user copy/paste the new libusbx descriptor structure as is, use that > in their app exclusively and then use a cast. This is what I am currently > pointing out to do in the NEWS update. I realy do not like this idea. Structures defined by the API should not be redefined by the application. That is the source of more problems later. > +* Fix unwanted cancellation of pending timeouts as well as amjor timeout > related bugs amjor -> major > +* Add Cypress FX/FX2 firmware upload sample, based fxload from > + http://linux-hotplug.sourceforge.net based fxload -> based on fxload I also submitted a new patch at https://github.com/libusbx/libusbx/pull/44 Bye -- Dr. Ludovic Rousseau ------------------------------------------------------------------------------ How fast is your code? 3 out of 4 devs don\\\'t know how their code performs in production. Find out how slow your code is with AppDynamics Lite. http://ad.doubleclick.net/clk;262219672;13503038;z? http://info.appdynamics.com/FreeJavaPerformanceDownload.html _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
