-
Notifications
You must be signed in to change notification settings - Fork 161
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add a way to exit GAP immediately, with an exit code. #365
Comments
Would it be enough to add a one-argument version of QUIT_GAP() and FORCE_QUIT_GAP()? |
Or, what's wrong with QUIT_GAP and FORCE_QUIT_GAP already? :) (you may have missed them being added). |
@ChrisJefferson isnt' this something what you've done recently ? |
Great! But I wasn't aware of it. I searched my email archive, I found an email by @ChrisJefferson from October 2014 that he wants to modify In fact, it doesn't seem to be documented at all: I just re-run |
Argh, never mind. For some really stupid reason, GAP picked up the manual from another, older GAP installation (a matter of a badly placed symlink). Fixed that, so now I see Still think it would be nice to mention it in an |
BTW, PR #150 is marked for GAP 4.8.0 milestone. |
Currently, I have to use
IO_exit
for that, but as was explained in #364, this is not so nice for various reasons.Such a feature is very important if one wants to properly script running GAP computations. E.g. when building the manual, or running tests, being able to set an exit code in order to signal the build system that there was a failure.
The text was updated successfully, but these errors were encountered: