Stephen Warren wrote: > It'd be nice if all symbols (types, values, functions, etc.) were all > prefixed with e.g. "IRR_"/"irr_" to ensure they never conflict with any > other library.
ACK for the public functions, definitely. I highly prefer lower case. > Is this library intended to support anything other than Pronto codes > (e.g. CIR, RC5, ... encode/decode)? If not, naming the library something > with "pronto" in the name seems like a good idea (ignoring trademark > issues anyway.) At least, something much less generic would be good. Damnit, I meant to mention this... > Doesn't the LIRC project have a library that does this kind of thing > already, that could be re-used instead of re-inventing the wheel? In > fact, don't they have a big database of key codes that might be useful? I was going to go do some research on if another library already did this, actually, but never got around to it. If another library already supports the actions we're looking for with a decent API, we shouldn't merge our own without good reason. -- 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
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://sourceforge.net/services/buy/index.php
_______________________________________________ concordance-devel mailing list concordance-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/concordance-devel
