On Feb 12, 2013, at 3:41 AM, Kustaa Nyholm <kustaa.nyh...@planmeca.com> wrote:
> On 12.2.2013 12.29, "Hans de Goede" <hdego...@redhat.com> wrote: >> >> I know, but I'm operating under the assumption that Nathan will eventually >> do a libusb release with his code, at which point having API compatibility >> would be good. And yes I know we don't completely agree on this :) > > I disagree having API/ABI compatibility for new features, even in > libusbx-1.0.x line of development, the sooner we break it the > better, now we are towing to their (libusb) decision making and that > what we wanted to get rid of when we forked. See below: > >> >> LIBUSB_HOTPLUG_EVENT_DEVICE_ARRIVED: A device has arrived and is ready to >> use >> LIBUSB_HOTPLUG_EVENT_DEVICE_LEFT: A device has left and is no longer >> available >> >> Not the best names ever, I would have called them ADDED / REMOVED > > see, stupid names but if we are stuck if we want to maintain API > compatibility > with libusb. Using descriptions like "stupid" for the proposed event names does nothing to advance the discussion on what the API for libusb 1.0 should look like. You, and others, have been given (and still have for a short time) an opportunity to help define the official hotplug interface for the libusb 1.0 API. I like the names ARRIVED/LEFT as they reflect more than just the device has been plugged in/unplugged. Device arrival signals the device was plugged in, enumerated by the os, matched by os drivers (if any exist), and finally enumerated by libusb. Left was chosen to match. We could still use ADDED/REMOVED (or MATCHED/TERMINATED, ENUMERATED/TERMINATED, etc) if that is what developers would rather see as part of the API. -Nathan ------------------------------------------------------------------------------ Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
