Batch returns after FOR command

[Jack]

Tom

BINGO!

That did the trick.

Thanks a whole bunch

Jack

 

[Mark Zbikowski \(MSFT\)]

"Call" just nests within CMD's data structures.

CMD /C starts an entire new process.

You cannot easily simulate CALL :label with a CMD /C since this may have
side effects.

 

[Karl Bernard]

So, for clarity, with "CALL" I could call (jump to) a label within the same
script (much like a GOTO), or call another script?

I understand that CMD invokes another interpreter, so I guess using CALL
could also be more "resource friendly" by invoking fewer new processes?

Thanks,

Karl

 

[Mark Zbikowski \(MSFT\)]

CALL is like a subroutine call. It does NOT launch another CMD.

CMD *is* the command interpreter. So doing CMD /C is invoking
another process.