views:

55

answers:

2

I have seen some code in which the arguments passed to the function by value was being modified or assigned a new value and was being used like a local variable.

Is it a good thing to do? Are there any pitfalls of doing this or is it Ok to code like this?

+1  A: 

No problems at all that I can think of. The arguments will either be placed in the current stack frame or in registers just like any other local variable. Make sure that the arguments are passed by value, however. In particular, arrays are passed by reference.

Mick Sharpe
+2  A: 

Essentially, a parameter of a function is a local variable, so this practice is not bad in principle.

On the other hand, doing this can lead to maintenance headaches. If another programmer comes along later, he might expect the variable to hold the passed in value, and the change will cause a bug.

One justification for reusing the variable is for a misguided notion of efficiency of memory usage. Actually, it can't improve efficiency, and can decrease it. The reason is that the compiler can automatically detect if it is useful to use the same register for two different variables at two different times, and will do it if it is better. But the programmer should not make that decision for the compiler. That will limit the choices the compiler can make.

The safest practice is to use a new variable if it needs a new value, and rely on the compiler to make it efficient.

UncleO
From the compiler's perspective, every assignment to an existing variable can be treated as a new variable. So the compiler can make the code just as efficient whether the programmer created a new variable or not. In fact, most microarchitectures have register renaming anyway, so the compiler doesn't even have to bother.
Eric Seppanen