bj_forLoopAIndex

is using bj_forLoopAIndex faster than using local integer for looping?
are there any side effects?

its all the same :P just tat using bj_ thingy then u wont need to declare it again, since its declared at init

I am not sure about that, it would be the same if bj_'s are just global variables,
but I am not sure they are.

one think i can think of is that they are global variable, and that they are declared at init. therefore it will be faster to use them, than to declare new local

Globals and locals (non-arrays) are so rediculously cheap that discerning any difference is impossible, and also pointless.

Yeah you are probably right,
I just wante to know if there is anything special about bj_'s

Like for example GetTriggerUnit() is preserved after waits...

globals are slower than locals and are... globals, using them as loop counters is not "cute".

Kind of began to post pleanty of time before the replies, the thing is that all bj_ are just global variables and don't get "preserved" by waits or anything like that.

Well that is what I needed a definite answer.

only vex have the skill for tat..

Writing bj_forLoopAIndex every time when looping is kinda annoying too.

Use locals. Use locals. USE LOCALS.

Ignoring that vex says they are faster, and that "bj_forLoopAIndex" will make your code stretch off the screen: global iterators would cause you incredible pain.

If you use global iterators, calling a custom function may change your iterator. That means you need to remember every iterator every function uses. If you forget one, and call that function from a loop using the wrong iterator, your loop will behave erratically and it will take at least 10 minutes to find the problem; IF YOU EVEN NOTICE IT. I can not emphasize enough how bad this is once your map starts getting complex.

There is a reason global variables get a lot of hate.

nah, I think I will use globals just to piss ppl off.

Amen.

Freedom of choice above all!