softdevbuilttolast.wordpress.com

thedeepbluecpp.blogspot.com

The Deep Blue C++: August 2014

http://thedeepbluecpp.blogspot.com/2014_08_01_archive.html

The Deep Blue C. Guidelines and musings on C programming. Wednesday, 13 August 2014. Guideline 9. Keep functions short and cohesive. A function should achieve its purpose by means of a cohesive structure. A function can be primarily structured in one of these ways:. Do not combine these structures in a way which makes it hard to follow the code flow throughout the function, or that it makes it difficult to test. A function should have a small cyclomatic complexity. One function, one purpose. But, you say...

thedeepbluecpp.blogspot.com

The Deep Blue C++: Bibliography

http://thedeepbluecpp.blogspot.com/p/bibliography.html

The Deep Blue C. Guidelines and musings on C programming. This is a list of all the bibliography referenced in this blog, ordered by author and year of publication. After each reference, you will find the list of articles which mention it. Steve McConnell: Code Complete, 2nd Edition. Microsoft Press, 2004. Bertrand Meyer: Object-Oriented Software Construction, 2nd Edition. Prentice Hall, 1997. Scott Meyers: Effective C : 50 specific ways to improve your programs and designs. Addison Wesley, 1998. From ou...

thedeepbluecpp.blogspot.com

The Deep Blue C++: Guideline 8. Define variables as close as possible to where they are used

http://thedeepbluecpp.blogspot.com/2014/06/guideline-8-define-variables-as-close.html

The Deep Blue C. Guidelines and musings on C programming. Saturday, 28 June 2014. Guideline 8. Define variables as close as possible to where they are used. Define variables as close as possible to their first use. Prefer variables with the most local scope as possible. Do not reuse a variable for two totally different things inside the same function body, just to "save some space". It kills readability and it is very error prone. But what is a variable definition, anyway? On the software Q&A site Stack ...

thedeepbluecpp.blogspot.com

The Deep Blue C++: January 2014

http://thedeepbluecpp.blogspot.com/2014_01_01_archive.html

The Deep Blue C. Guidelines and musings on C programming. Sunday, 26 January 2014. Guideline 4. Avoid fall-through in nonempty cases of "switch" statements. Label in a switch statement shall be followed by one of the following:. A set of one or more statements, each in its own line, terminated by a break. We may call "empty case" a case. Label which is followed by either another case. Instruction. These statements shall not lead to a fall through another case. If there is one;. Label), the execution will...

thedeepbluecpp.blogspot.com

The Deep Blue C++: November 2014

http://thedeepbluecpp.blogspot.com/2014_11_01_archive.html

The Deep Blue C. Guidelines and musings on C programming. Saturday, 15 November 2014. Guideline 10. A function should have a single exit point at its end. Prefer a single exit point. In void functions, the single exit point should be the physical end of the function. In non-void functions, the single exit point should be a return. Statement at the last line of the function. Statement should be simple and avoid implicit type conversions. Prefer not to throw exceptions. In void functions, a return. Stateme...

thedeepbluecpp.blogspot.com

The Deep Blue C++: April 2014

http://thedeepbluecpp.blogspot.com/2014_04_01_archive.html

The Deep Blue C. Guidelines and musings on C programming. Wednesday, 16 April 2014. Guideline 6. Ensure entry and exit conditions in loops. Ensure entry and exit conditions in loops. Write code that guarantees that loops will be entered and exited correctly. Be aware of the possibility of an infinite loop and prevent it. Guideline #5 was focused in discussing how for. Loops should be. But it also contained some discussion about choosing a loop structure. Let's review it:. Or a do . while. It is easy to c...

thedeepbluecpp.blogspot.com

The Deep Blue C++: March 2014

http://thedeepbluecpp.blogspot.com/2014_03_01_archive.html

The Deep Blue C. Guidelines and musings on C programming. Monday, 10 March 2014. Welcome to The Deep Blue C. The region of my brain which stores this kind of knowledge is starting to be a bit crowded, but it still needs free space to learn new things. And my memory doesn't grow. What if I forget some useful bit of knowledge which I should apply tomorrow? Software programs have two kinds of audience. They are written for a computer to execute them, but also for people to read and hopefully understand ...

thedeepbluecpp.blogspot.com

The Deep Blue C++: Guideline 10. A function should have a single exit point at its end

http://thedeepbluecpp.blogspot.com/2014/11/guideline-10-function-should-have.html

The Deep Blue C. Guidelines and musings on C programming. Saturday, 15 November 2014. Guideline 10. A function should have a single exit point at its end. Prefer a single exit point. In void functions, the single exit point should be the physical end of the function. In non-void functions, the single exit point should be a return. Statement at the last line of the function. Statement should be simple and avoid implicit type conversions. Prefer not to throw exceptions. In void functions, a return. Stateme...

thedeepbluecpp.blogspot.com

The Deep Blue C++: June 2014

http://thedeepbluecpp.blogspot.com/2014_06_01_archive.html

The Deep Blue C. Guidelines and musings on C programming. Saturday, 28 June 2014. Guideline 8. Define variables as close as possible to where they are used. Define variables as close as possible to their first use. Prefer variables with the most local scope as possible. Do not reuse a variable for two totally different things inside the same function body, just to "save some space". It kills readability and it is very error prone. But what is a variable definition, anyway? On the software Q&A site Stack ...