On 2012.04.22 10:27, Vincent Pelletier wrote: >> I'd have libusbx everywhere, starting with soname, header >> name, directory names, as well as API prefixes. > > I think this would be The Right Way (tm).
I think we share the same view here, but we also have to acknowledge that we are a minority. If many others have voiced their concern, as well as their preference for a different approach, the best we can do is register our vote and explain the reasons for our choice, but that's about it. Right now, even with a compatibility layer, I don't think there is much incentive to divert resources for an additional libusb -> libusbx renaming effort, even more so as we would prefer if users chose one rather than try to use both. But that doesn't mean that, once the dust settles, and if we think that's achievable, we're not gonna look into trying to satisfy both sides. Regards, /Pete ------------------------------------------------------------------------------ For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
