Yeah, I feel I'm being a bit picky here. BUT... trying not to compare this to other languages...
Quote: "Dwords can never be negative so your for/next loop never terminates"
exactly, my point is here that the condition for a negative value should never occur.
1-1 = 0
1 and 0 are in the range of a DWORD values.
The compiled .exe should know when 0 is reached from the for/next statement with step -1. That condition should be met before any condition that leads step -1 to go pass 0. Thus, a DWORD value range should have no factor in this case, because like i said, the for/next -1 counter should never go under 0.
Yes, I know im in the land of work-arounds. My work-around was just to do something like:
for local_index = 10 to 1 step -1
` blah blah
next
and then compare it with what I needed with a -1 to it... like "SomeVariable> (local_index-1)" ... so (local_index-1) could be 0 to be compared with in my program's code proper.
logically to me, # to 0 step -1 on a DWORD type should indeed work. Once step -1 get's to 0, get'r done!