Open Mysticial opened 6 years ago
Version 0.7.6.9484 adds a pause:-2
which should force even errors to not pause. I haven't had the time to really test it yet.
Logging of errors to a file is non-trivial and will be deferred to a future release.
No longer a bug as it's been patched. But lot of internal cleanup needed internally to make this right.
When the program errors out, it will sometimes ignore the
pause:-1
option and pause anyway waiting for the user to pressENTER
.Initially this was by-design. As the user will usually want to know about errors. But I've already had 2 requests to suppress the pause even in the event of an error.
The correct solution is to dump the errors to a log file and exit with the appropriate error code so it can be picked up by scripts.
Internally, the error/exception handling is a mess. Half of the program properly uses C++ exceptions. The other half does an "error-and-exit".
Code that properly uses C++ exceptions will gracefully unwind the stack. When control goes back to
main()
, it is printed out and exits normally (with the proper pause behavior).For the other half of the program that hasn't migrated to the new system yet, it will simply error-and-exit bypassing the proper pause behavior.