'
It's great to see someone else do all the work, and you are using jeb's appending, and you timed it and draw your conclusions, I really appreciate, thanks ben
ps.: I myself time by watching the clock, I'm so lazy
Limit CMD processing to internal commands, safer and faster?
Moderator: DosItHelp
Re: Limit CMD processing to internal commands, safer and fas
There is also another possible way to process the internal SET command, without disabling pathext.
There seems no difference in speed, wether you use safeSet or pathExt=: (the path should be still empty).
But one curious effect is that it fails when I change it to
Then it tries to call a file named "set<space>.bat".
I can't see the reason why it depends on the second caret.
Code: Select all
set "safeSet=set^ ""
call %%safeSet%% var=123"
There seems no difference in speed, wether you use safeSet or pathExt=: (the path should be still empty).
But one curious effect is that it fails when I change it to
Code: Select all
set "safeSet=set^ ^""
Then it tries to call a file named "set<space>.bat".
I can't see the reason why it depends on the second caret.