Am 02.04.2010 11:02, Matthias Melcher wrote: > > On 02.04.2010, at 10:04, MacArthur, Ian (SELEX GALILEO, UK) wrote: >> Another thing - if we are doing the conversion anyway, should we think >> about converting all the tabs into spaces to "fix" the layout "once and >> for all" and dodge around that fact that I (and I assume others) have >> different tab settings for different projects and keep getting >> confused...! > > Absolutely. > > Thanks for the hint.
Would that help? I don't think so. I'm used to have the correct tab settings (8) for FLTK and other projects (my job). My editor(s) add mixed tabs and spaces for indenting. I could change that for FLTK, but ... then *I* would have to manage different settings for different projects, and others maybe too. Do you see the point ? Whatever we choose ... But while we're at it, one more observation: trailing spaces, especially in "empty" lines between indented code lines. Some editors align empty lines with the code above and below, so that we get e.g. lines with only 4 spaces (I know that my editors do that, but I try to remove the spaces whenever I notice). Now I saw in Ian's latest commits (e.g. r7399-7402) that he (or his editor, maybe automatically ?) changed some lines by only cutting off trailing spaces. The annoying effect is that there are lots of diffs where no real diffs are. Question: should there also be a rule to cut trailing spaces before each commit? Would indent be able to do that? To the question about an automated indenting tool: Matt wrote "preferred on Mac" or similar. If we apply such a tool, then *all* developers need access to the *same* tool an *all* platforms, otherwise we'd have chaos after a short time. I think that Duncans proposal to use indent and define some options of indent be the standard (and write them down in the CMP) would probably be the best compromise, even if we can't retain the current FLTK standard. At least we would then have a real standard. P.S. I thought of using the tool permanently, but if we would use it only once, then some things might be different. Albrecht _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
