On Fri, 30 Mar 2007, Brian Foster wrote:
> apologies if I'm coming across as a bit strident, but besides just
> returning from the pub ;-) the tendency to conflate the
> conformance of source code to some stone tablet with the code's
> functionality and quality is one of my "Hot Buttons".
I second you on style being a minor issue, agreement and consistency
(on and in whatever style) being the important matter. However, I
disagree with you that style has no bearing on quality.
Certain "styles" can impact /directly/ on functionality, e.g.
old-style type-less K&R function declarations may not be type-checked
by the compiler.
Readability is crucial for maintaining code: Little things like
putting function names at the beginning of the line aid greppability.
CamelCaseVariableNames are tedious to type and, compared to
saner_variable_names with words spaced in a more natural way, are
difficult to read.
In short, style /can/ have a functional impact on code, on
maintainability over time foremost.
Paul Jakma paul at clubi.iepaul at jakma.org Key ID: 64A2FF6A
You can't cross a large chasm in two small jumps.
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!