On 2013.05.17 09:46, Hans de Goede wrote: >> but that'd mean changing the API... > > Right, which as we learned with the MaxPower is a complete no no,
Not really. The only thing I learned is that we'll have to wait a bit longer for people to reach enlightenment about this whole API breakage bullshit. As a matter of fact, some unlikely people have already made a first step towards that [1]... ;) > I rather dislike the extra ctx parameter too, so I've implemented the > proposed libusb_get_port_numbers and libusb_get_port_path is now a wrapper > around it. Thanks. I would have sent a patch too, but I wanted to make sure there weren't any major objections. Less work for me! > As said before the intention is to leave libusb_get_port_path > around in the 1.0.x series for both ABI and API backward compat reasons. Yeah. Alas people are not yet ready to be unplugged from the stable API/ABI Matrix illusion... Regards, /Pete [1] https://www.kernel.org/doc/Documentation/stable_api_nonsense.txt ------------------------------------------------------------------------------ AlienVault Unified Security Management (USM) platform delivers complete security visibility with the essential security capabilities. Easily and efficiently configure, manage, and operate all of your security controls from a single console and one unified framework. Download a free trial. http://p.sf.net/sfu/alienvault_d2d _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
