1. Minimize pointer use. Don't de-reference a NULL pointer. Don't use pointers to void as a polytype to defeat the type system, such as it is.
This is a no brainer, pointers are FINE if they're used as constant pointers from accessors in a modular API that nobody but a really godo idiot can break.
2. One declaration per line, in alphabetical order, using meaningful names.
This is style, but very GOOD style
3. Some form of hungarian notation so variable type is known without hunting all over for the declaration.
For CVI this is a good idea even if it's just throwing val str or ptr onto the variable name somewhere to get an IDEA of what we're working with, in other IDE's it's not such a big deal, in VS, I just mouse over the identifier.
4. No "magic numbers".
unless it's like [BUFFERLEN-1] or other relatively idiot proof ones, even then I tend to comment...
5. Use the registry, not .ini files
This depends on the implementation and distribution method, we use ini's alot because we run alot of our software off remote drives, however I do tend to agree.
6. Use the
if ((iStatus = function ()) != NO_ERROR) {
// error handling here
}
idiom.
Eww... first row open brackets, bad readability and brackettracing.
7. Use a consistent brace style, normally the "one true bracket style."
Style my friend, it's all good so long as it's condusive to good development and is consistant.
8. Annotate - good code's written once and read many times.
Just dont' say "this is an integer"
9. Limit nesting depth, function length, number of parameters, module size.
functions should do one thing and do it well, if that one thing encompasses other smaller related things, they should each be functions, lather rinse repeat.
10. Don't code memory leaks.
Tell that to Microsoft.
11. Don't recode stuff that's in the standard library.
Unless it's academic in nature.
