-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Other possible style to use on.exit
#1758
Comments
Imagine R keeps a list of commands which need to be executed when exiting. The current implementation allows you to do one of three things:
What you have suggested is not wrong, and it even makes sense if you only call |
I can understand your point, some |
I've learned
on.exit
in the book and it is really helpful. But setting the parameteradd
to TRUE get me a little puzzled, and theafter
argument might just make it harder to know the order of expressions. If the contents inon.exit
would just run in the end, why not wrap them up? Which mean:could be used as:
In this style, we do not have to figure out which codes would be evaluated first. Wonder if this style would be better.
Thanks.
The text was updated successfully, but these errors were encountered: