Greg wrote: > I'm -1e9 on redefining tabstops, or changing the coding standards.
IMHO, the best way forward is to play around with the options for code formatters (eg astyle, indent, uncrustify as posted earlier) to get the closest match for the current coding standard. I doubt it will be a 100% match for whichever tool. Then adopt the tool and these options as the new coding standard. It won't please everybody, but then the current guidelines don't anyway, but it will be easy to apply the standard using the tool. We document the tool and options in the CMP / Coding Standards. So the base options we are looking at are: K&R, tab=8, indent=2. Then there's stuff not in the CMP, but already in the code, for one-liners such as "if (x) y;", "for (x) y;" and "while(x) y;". It might take a while to refine all the options to get close to the current CMP / Coding Standards. And I don't think that we should be looking at customising any of the tools, or providing patches, or requesting new features. D. _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
