Linked by Thom Holwerda on Tue 15th Jan 2013 21:24 UTC
General Development "I was really excited to write this article, because it gave me an excuse to really think about what beautiful code is. I still don't think I know, and maybe it's entirely subjective. I do think the two biggest things, for me at least, are stylistic indenting and maximum const-ness. A lot of the stylistic choices are definitely my personal preferences, and I'm sure other programmers will have different opinions. I think the choice of what style to use is up to whoever has to read and write the code, but I certainly think it's something worth thinking about. I would suggest everyone look at the Doom 3 source code because I think it exemplifies beautiful code, as a complete package: from system design down to how to tab space the characters." John Carmack himself replies in the comments.
Thread beginning with comment 549081
To read all comments associated with this story, please click here.
pretty good
by bnolsen on Wed 16th Jan 2013 22:35 UTC
Member since:

Except for the formatting part our current code base uses much the same, with generally Qt type function names and naming conventions. Minimal use of inheritance, generally things are structs with functions, heavy heavy use of const everywhere.

It's a pretty effective style of coding, easy to maintain and debug. One technicality was the improper ordering of the const stuff and not constifying enough when pointers passed in

example parameter

type ** value

would be better expressed as:

type * const * const value

so the function won't hose itself if the function writer improperly reassigns one of the levels of "value" instead of just the contents.

Reply Score: 2