On 2012.04.23 11:57, Kustaa Nyholm wrote: >> In its current implementation, as I explained, I very much see Peter's >> versioning buggy as it unnecessarily breaks cross-platform, > > This is not clear to me, someone cares to educate why and how this > breaks cross-platform.
OK, maybe you are confused by the fact that I am using platform as a build environment rather than an actual platform system (mostly because Windows could be considered as 3 slightly different systems depending on whether your libusbx based app was built with cygwin, MinGW or MSVC). I would say that our goal of being cross platform implies trying to support the major build environments for each system. But if you think using "cross-platform" is a misnomer for that, I'll try to be more explicit. > Crashing is not nice, although a fast and consistent crash with clear > indication of the issue is acceptable. Compile/link and/or load error > would be best. I think Hans' and probably Michael's views are mostly with regards to a libusb compiled app, using a shared libusb library that has been replaced with libusbx. Since we're dealing with extra field, compilation should always break and force a developer to update, so the crash is only expected to apply for apps that were using a shared libusb library and where that shared library has been replaced with libusbx. This is of course something we want to consider (officially our goal is to be a "drop-in" replacement), but the question is how far we are willing to go for such a scenario, and what the implications are. > Just to ensure I understand the issue, please tell me if this is > correct (I've not looked at the code, all this is based on > monitoring the libusb lists): > > There is a new function function (in 1.0.9) in both libusb and > libusbx. This function takes and argument of type libusb_version, > and this type has different structure in the two libusbs, namely > libusb has added two fields. Correct. > If so, then there is no code utilizing that new functionality > and thus compatibility with existing code is a moot point That's also how I see it. 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
