>> I don't think rejecting tabs is a good idea, as there should really >> be no problem if people use spaces or tabs or both as long as they're >> used 'correctly'. The only time a problem comes up is when editors >> are set to have tab stops set to odd things.
> But people do do that, all the time. There are a lot of problems that > are theoretically non-problems if everyone would just configure the > same, but people don't do that. I was surprised by the code format in one of fltk2 UTF-8 routines last night, and was wondering whether different coding standards applied, so I've been looking through the CMP at http://www.fltk.org/cmp.php Under the General Coding Style section, there's a minimal K&R example followed by: "Each block of code must be indented 2 spaces. If you use tabs, they must be set at every 8 character columns; this is different than the Microsoft standard of 4, but you can change that to match UNIX." So the FLTK standard already specifies TAB as 8 spaces, but it doesn't seem to help because people are either unaware, or their editors are not set up correctly. On a vaguely related note: I came across the MPlayer developer FAQ last night, which outlines the requirement that a code commit either contains a format change, or a code change, but not both. It even says that indenting more than 5 lines of code if you add an if around a code block is not allowed in the same commit. Food for thought... D. _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
