Thread: guys i really need help! else if ..

Originally Posted by quzah

It is easier for me to locate counter where I expect it (at the top of the current block, or the top of the function) than to have to hunt for it on every single one of those 100 lines.

Actually, you still have the problem of locating the point where counter was last assigned a value. But in this case, I'd say the problem really is:

Originally Posted by \007

Code:

/* 100 lines later */

With shorter functions that do one thing and do it well, the problem of locating the declaration disappears, and declaring variables at the top is less problematic because the scope is already reduced.

Originally Posted by quzah

See, you aren't even doing it right now:

Agreed, unless there is a special reason to do so, the scope of i should not extend beyond the loop.

Originally Posted by Matticus

If this causes confusion or "error because I may have assigned it to something else between here and up there," then that just means I would have to correct and learn from that error.

Prevention is better than cure.

Originally Posted by \007

Yes, I rather place it inside the loop's scope but C89 wouldn't allow that. It was just an overly simple example.

C89 wouldn't let you do what you did before that either:

Code:

int main(void)
{
  /* 100 lines later */

  int i, counter = 10;
  for(i = 0; i < counter; i++)
    printf("%d\n", i);

  return 0;
}

You can't do that in C89 unless right before there, you start a new code block - and then if you are doing that, you are doing it the "old style" anyway, so your argument is self defeating.


Quzah.