Hi Quentin,
I like the style guides overall, but I would like to propose one
change. Rather than specifying spaces for indenting, I would like to
see a single tab used for semantic indenting (i.e. inside each
block), and spaces used after that for alignment. This allows you to
do things like this (note that this will only work in a fixed with
font):
[object doSomethingWith:this // This is the first argument
andAlso:anotherThing] // This is the second
And have the colons and comments line up whatever the user sets their
tab width to. If we use spaces, then the only way a user can change
the indent width is to replace a sequence of 4 spaces with n spaces
(or a tab), which will destroy this kind of alignment. If we just
use tabs, then the same applies (it's slightly easier to change the
indent width, but we still lose alignment). By using this
combination, we give developers flexibility as to how they view the
indenting, but still retain a clear and readable body of code.
I would also like to see a rationale section added to each part of
the guidelines. That way people can see that we have picked them for
a sensible reason, rather than just made arbitrary choices.
David
_______________________________________________
Etoile-dev mailing list
[email protected]
https://mail.gna.org/listinfo/etoile-dev
