Stephen Satchell wrote:
> I get burned on this from time to time, especially after working on PL/I
> code. In my programs, I have a style rule that says that an empty
> statement of a for, while, do, or if statement must be coded as {} in order
> to show that the set of instructions to execute is empty. (I also have the
> style rule that EVERY for, while, do, or if statement must have the object
> instruction(s) enclosed in braces -- I got this from Plauger's book and it
> has helped immensely.)
I totally agree with you.
Maybe yeah, it's more keystrokes. Yeah, code looks larger'n'stuff.
But what matters in big projects such as the linux-kernel; it must be as
maintainable as possible! So any codingstyle that makes things more
readable/
less prone to errors should be encouraged.
In my opinion, the kernel is also rather under-documented, so
to say.
-- ------------------------------------------------------------ Folkert van Heusden http://www.vanheusden.com/ some e-mail addresses: f.v.heusden@ftr.nl, flok99@dds.nl mobile phone: +31-6-22390057- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue Feb 29 2000 - 21:00:10 EST