I had thought about that, but I have tested with a very complex For Next
loop and I still couldn't see the difference.
As Tom says it would be bad news if the compiler would be thrown by that.
Clever bits of software these compilers, especially at the speed they do it.

RBS

"David Cox" wrote in message
...
I think perhaps you are all testing with nicely structured code. If you
sprinkled a few ifs and gotos around, wandering all over the place, like us
old fashioned real programmers used to do, the the compiler may not be able
to link a particular NEXT with its matching FOR without the variable
specified, and have to generate more complex code.

just a theory


"RB Smissaert" wrote in message
...
Read in the book Visual Basic for Applications in 21 days by Matthew
Harris (third edition) that putting the loop counter after the Next would
make the loop faster:

For i = 0 to 10
'code
Next i

I can see it makes the code clearer, but I didn't think it made it any
faster and on simple testing I can see no difference:

Option Explicit
Private lStartTime As Long
Private Declare Function timeGetTime Lib "winmm.dll" () As Long

Sub StartSW()
lStartTime = timeGetTime()
End Sub

Sub StopSW(Optional ByRef strMessage As Variant = "")
MsgBox "Done in " & timeGetTime() - lStartTime & " msecs", , strMessage
End Sub

Sub test()

Dim i As Long
Dim c As Long
Dim n As Long

StartSW

For i = 0 To 10000
For c = 0 To 1000
n = i + c
Next
Next

StopSW

End Sub


Is there any truth in this?


RBS