Hey all,

I'm planning on making what *SHOULD* be an innocuous change to the code that
will touch LOTS of stuff.

Currently every time we construct a USB message we _assume_ the extra 0-byte
that windows wants, and then we throw it away for the non-Windows case. This
is silly on a few levels: (1) anyone who knows USB but doesn't know windows
is gonna get thrown off by this (2) it's a lot of duplication we can unify
in one place. You could also make a few other arguments against it, but
those are the big ones.

So I plan to switch this. Everywhere a USB message is constructed I'll NOT
include the extra 0-byte and then I'll ADD a 0-byte in the Windows code.

Does anyone have any objections to this or concerns?

-- 
Phil Dibowitz                             [EMAIL PROTECTED]
Open Source software and tech docs        Insanity Palace of Metallica
http://www.phildev.net/                   http://www.ipom.com/

"Never write it in C if you can do it in 'awk';
 Never do it in 'awk' if 'sed' can handle it;
 Never use 'sed' when 'tr' can do the job;
 Never invoke 'tr' when 'cat' is sufficient;
 Avoid using 'cat' whenever possible" -- Taylor's Laws of Programming


Attachment: signature.asc
Description: OpenPGP digital signature

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
concordance-devel mailing list
concordance-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/concordance-devel

Reply via email to