Ziggy:
I don't exaclty disagree wirh you. I have for a while been toying with the idea of declaring variables closer to where they're used simply because it's a pain to have to go searching for them when the place they're being modified is somewhere else. Like a function which might return some data in some globals. Declaring those near the function that uses them would keep the stuff together. On the other hand it would make it harder to look at the set of functions and see what globals are there for you to access. So... tradeoffs.
Of course this isn't exactly what you're talking about doing.
So maybe I'll take another look at declaring variables in different places. But I'm not gonna do this crap very often.
Local biggestValue:Float=Sqr(fourBiggestSquaredMinus1+1.0)*0.5
I hate when people do that. I only do that when I have to because I need to set a variable at the start of a type delcaration. It looks messy.
I don't exaclty disagree wirh you. I have for a while been toying with the idea of declaring variables closer to where they're used simply because it's a pain to have to go searching for them when the place they're being modified is somewhere else. Like a function which might return some data in some globals. Declaring those near the function that uses them would keep the stuff together. On the other hand it would make it harder to look at the set of functions and see what globals are there for you to access. So... tradeoffs.
Of course this isn't exactly what you're talking about doing.
So maybe I'll take another look at declaring variables in different places. But I'm not gonna do this crap very often.
Local biggestValue:Float=Sqr(fourBiggestSquaredMinus1+1.0)*0.5
I hate when people do that. I only do that when I have to because I need to set a variable at the start of a type delcaration. It looks messy.