MS-DOS's batch file interpreter is about 35 years old and has been through countless revisions. It is still the default batch file system for Windows (despite Microsoft pushing PowerShell). And it _still_ has no way to determine whether a batch file executed successfully :(
-
-
This Tweet is unavailable.
-
I think the point here, is why would you need another script language to script native OS events. Python offers way better mechanisms I agree
End of conversation
-
-
-
I suppose you could save the errorlevel to a separate variable after every command...
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Even with powershell and extensive time devoted to building scripts, Microsoft's command line makes me want to flip tables
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
You using someone else's batch files?
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
and has no native file compression included!! In general, I keep my distance from PowerShell, but sometimes is the only way.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
OTOH bash “set -e” design really work either. One liners in Makefile usually works. But not always. Software is just broken! Now, there *are* some great bat files out there :)
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
-
(feel free to exit /b %ERRORLEVEL% if you want to preserve the original return code, although I rarely care beyond 0/not 0)
End of conversation
New conversation -
-
Show additional replies, including those that may contain offensive content
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.