Programming Proverbs 11: Use intermediate variables properly

re: Programming Proverbs 11: Use intermediate variables properly

Henning Krapoth — Thu, 15 Mar 2007 09:41:06 GMT

x = a + b * (sqrt(y) + w)

and turns it into something like this:

var1 = a + b

var2 = sqrt(y) + w

x = var1 * var2

You might be getting different results with these ;-)

re: Programming Proverbs 11: Use intermediate variables properly

Yousuf — Thu, 15 Mar 2007 13:37:34 GMT

x = a + b * (sqrt(y) + w)

and turns it into something like this:

var1 = a + b

var2 = sqrt(y) + w

x = var1 * var2

Yes, the correct code example should be look like;

var = b * (sqrt(y) + w)

x= a + var

and for the sake of post "Intermediate Variables...";

var1= sqrt(y) + w

var2= b * var1

x = a + var2

re: Programming Proverbs 11: Use intermediate variables properly

Alfred Thompson — Thu, 15 Mar 2007 17:31:04 GMT

The last couple of comments show three things. One is that mesing with too many intermediate variables can get one into trouble. And secondly one really does need to test their algorythms completely before putting them into a program. Lastly (until someone comments with more) that a good code review can go a long way towards improving quality. Thanks for the code reviews!

re: Programming Proverbs 11: Use intermediate variables properly

Rick — Thu, 15 Mar 2007 21:00:36 GMT

In my experience intermediate variables make source level debugging much easier too. They make it easier to see where in the overall calculation your error is.

re: Programming Proverbs 11: Use intermediate variables properly

Jeff — Tue, 20 Mar 2007 03:13:10 GMT

I second Rick's observation. The main reason I use intermediate variables is to make the code easier to inspect in the debugger.