- Sponsor
-
Notifications
You must be signed in to change notification settings - Fork 567
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
Comments
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Reviewer: Peter Bruin |
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 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-) |
comment:5
Replying to @pjbruin:
Would |
comment:6
Replying to @jdemeyer:
Yes, I think that is a very good solution. A bit longer, but more descriptive. |
comment:7
Name changed to |
comment:8
Attachment: 15124_pari_sig_on.patch.gz |
Author: Jeroen Demeyer |
comment:9
OK, all tests passed. |
Merged: sage-5.12.beta5 |
Up to now, the functions
sig_on()
and friends were redefined as_pari_sig_on()
for use insage/libs/pari.pyx
. This is a hack and should be fixed by providing (and exporting) properpari_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
The text was updated successfully, but these errors were encountered: