Skip to content
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

Make pari_sig_on() macros accessible #15124

Closed
jdemeyer opened this issue Aug 30, 2013 · 11 comments
Closed

Make pari_sig_on() macros accessible #15124

jdemeyer opened this issue Aug 30, 2013 · 11 comments

Comments

@jdemeyer
Copy link
Contributor

Up to now, the functions sig_on() and friends were redefined as _pari_sig_on() for use in sage/libs/pari.pyx. This is a hack and should be fixed by providing (and exporting) proper pari_sig_on() macros.

This ticket doesn't claim to fix all problems with PARI error handling, but at least it should improve the situation.

Also fix #10126.

Component: c_lib

Author: Jeroen Demeyer

Reviewer: Peter Bruin

Merged: sage-5.12.beta5

Issue created by migration from https://trac.sagemath.org/ticket/15124

@jdemeyer jdemeyer added this to the sage-5.12 milestone Aug 30, 2013
@jdemeyer

This comment has been minimized.

@jdemeyer

This comment has been minimized.

@pjbruin
Copy link
Contributor

pjbruin commented Aug 30, 2013

Reviewer: Peter Bruin

@pjbruin
Copy link
Contributor

pjbruin commented Aug 30, 2013

comment:4

This looks good to me. I was just thinking about this and had a very similar patch in mind (but with different names than pari_sig_on()/pari_sig_off(), which I still find slightly misleading).

I will run doctests and then give this a positive review - conditional on passing the tests of course, but not on the names for the macros. 8-)

@jdemeyer
Copy link
Contributor Author

comment:5

Replying to @pjbruin:

This looks good to me. I was just thinking about this and had a very similar patch in mind (but with different names than pari_sig_on()/pari_sig_off(), which I still find slightly misleading).

Would pari_catch_sig_on(), pari_catch_sig_off() be a good compromise?

@pjbruin
Copy link
Contributor

pjbruin commented Aug 30, 2013

comment:6

Replying to @jdemeyer:

Would pari_catch_sig_on(), pari_catch_sig_off() be a good compromise?

Yes, I think that is a very good solution. A bit longer, but more descriptive.

@jdemeyer
Copy link
Contributor Author

comment:7

Name changed to pari_catch_sig_*

@jdemeyer
Copy link
Contributor Author

comment:8

Attachment: 15124_pari_sig_on.patch.gz

@jdemeyer
Copy link
Contributor Author

Author: Jeroen Demeyer

@pjbruin
Copy link
Contributor

pjbruin commented Aug 31, 2013

comment:9

OK, all tests passed.

@jdemeyer
Copy link
Contributor Author

jdemeyer commented Sep 2, 2013

Merged: sage-5.12.beta5

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants