On Mon, 15 Oct 2012 09:56:29 -0700, Orin Eman said: >> 1) making libusb_control_transfer_get_setup not inline, so it's iffy cast >> is hidden in a .c file >> > >That should wait for the next API break as it would change the binary >interface.
By adding a new exported symbol you mean? Of course removing or changing a publicly visible symbol/API would be a bad idea, but is adding one really a problem? >I'd suggest implementing it as a #define and punting the problem to the >caller. Don't see how that helps... it's an inline function now, being a #define macro won't change much. >Another solution would be our unpopular friend, the anonymous union for the >transfer buffer. Aren't those new in C11? libusbx seems to be mostly C89. Even C99 usage is guarded by #ifs. Cheers, -- ____________________________________________________________ Sean McBride, B. Eng s...@rogue-research.com Rogue Research www.rogue-research.com Mac Software Developer Montréal, Québec, Canada ------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
