not true. Some conditions would only have to be parsed once. for example the incrememnt itself would be done in memory by mIRC. Using a while loop you have to manually include /inc %incvar wich means mIRC has to parse that command on each iteration _then_ perform the increment. Using for mIRC would handle it in memory and you dont have to include it. In some cases such as leaving off values they can be ignored entirely and not parsed at all. I Think for would be heaps faster than a while in comparison.
If it is added i would like to see multiple conditionals (added to while as well) such as
for (whatever;(some test) && (some other test);inc it) {
code
}
