>> As far as the guide, any argument about adding: >> >> - remove the bit about tabs, and say "indents are two spaces, tabs >> are >> not allowed"
I always worry that 2 is not enough, 4 looks more distinct. But 2's fine if that's what folk feel is good. IIRC, Linus always favours 8 (like a "real" tab used to be) on the basis that if the code starts to become deeply nested, that's a warning of sorts! Whatever we pick, it'll be a change from my regular style anyway, so I don't really mind what it is. >> - 80 column max for lines Hmmm, no, not if that is going to be rigidly enforced. I've had patches rejected by zealots elsewhere for creeping a few chars over the 80-char limit, and the reworked (wrapped) versions met the constraint but were bloody well unreadable. That is not an improvement. We used to work to 132 chars back when I was coding on a VT-100, so I can't really see why 80 is a step up. I wonder how much damage it would do to just pour the whole lot through indent (with suitable options set) and just see what comes out? It might work...! -- Ian _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
