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. ADDED/REMOVED is much better, though I would have chosen PLUGGED/UNPLUGGED ( PLUGGED_IN, PLUGGED_OUT) as this is hotPLUG we are talking about. br Kusti ------------------------------------------------------------------------------ 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
