How can I set a value to %%variable in the for /L loop?

[aGerman]

As mentioned before I don't see an easier way ...

I don't see any drawback from bars143's method, do you?

Well we are talking about nested loops. How do we return to the outer loop?

Even if you would find a way - how many times can you nest calling a lable without drawback?

Code: Select all

@echo off &setlocal
set /a "n = 0"

:foo
set /a "n += 1"
echo %n%
call :bar

:bar
goto foo

In my tests it counts until 705 then dies with the message that the maximum of recursions was reached.

Regards
aGerman

[foxidrive]

As mentioned before I don't see an easier way ...

I don't see any drawback from bars143's method, do you?

Well we are talking about nested loops. How do we return to the outer loop?

Even if you would find a way - how many times can you nest calling a lable without drawback?

Code: Select all

@echo off &setlocal
set /a "n = 0"

:foo
set /a "n += 1"
echo %n%
call :bar

:bar
goto foo

In my tests it counts until 705 then dies with the message that the maximum of recursions was reached.

Regards
aGerman

It wasn't for a nested loop (the discussion and participants moved on) - the last sample I commented on only uses one call.

[aGerman]

the last sample I commented on only uses one call

I see. In that case I'd say we shouldn't expect any problems. (even if we normally should return to the point where the label was called for my understanding)

i found out why "goto" does not execute when specified number 100 is reached

Ooo it's pretty difficult to examine what happens. You just discribed the behavior again.
It's an internal problem of cmd.exe that I would rather call a bug because ...
- Breaking works for other kinds of FOR loops but FOR /L. That implies that breaking a loop was intended by the developer.
- Breaking a FOR /L loop does't work properly even if it mostly looks like it would. We don't get any warning or error message though. That's what let me believe the developer wasn't aware of his fault.

Regards
aGerman

[einstein1969]

the only way i know for break a for /L loop is generating an error. But this is without sense.

Jeb introduce this trick for break an infinite for /L loop (1 0 1) for examples.

I used for speedup a code.

Don't work for nested loops. link

einstein1969

[Aacini]

@bars143,

All your questions and tests about the behaviour of a GOTO or CALL command placed inside a FOR /L loop had been discussed with detail in the threads indicated by aGerman above:

...

Of course we had some discussions about it. I started one of them
http://www.dostips.com/forum/viewtopic.php?t=2707
Also see
viewtopic.php?t=3487

Regards
aGerman

Antonio