Recent Features
| |||||||||||||
What every C Programmer should know about undefined behavior #2/3What every C Programmer should know about undefined behavior #2/3Posted Jun 8, 2011 13:39 UTC (Wed) by nix (subscriber, #2304)In reply to: What every C Programmer should know about undefined behavior #2/3 by cmccabe Parent article: What every C Programmer should know about undefined behavior #2/3
If you end up with a page worth of declarations, it makes it clear even to the dullest programmer that his function is getting too long.You have too much confidence in dull programmers. I have worked on functions with ten pages of variable declarations at the top. (The functions themselves were ten thousand lines long, which *anyone* should have realized was too long, but they had grown slowly to that length and nobody wanted to take the 'risk' of splitting them.)
(Log in to post comments)
What every C Programmer should know about undefined behavior #2/3 Posted Jun 16, 2011 0:05 UTC (Thu) by cmccabe (guest, #60281) [Link]
Heh, that sounds like a story from thedailywtf.com
Anyway, lazy or careless people can always find a way to do lazy or careless things. It is nice if you get a helpful hint that what you are doing is wrong, though. For example, using 4 or 8 space indents tends to give you a wakeup call that 20 levels of nesting might be more than the human mind can understand in C or C++. Using 1 or 2 space tabs does not. etc.
|
|||||||||||||