#9640: Change PARI error catching mechanism
----------------------------------------+----------------------------
Reporter: jdemeyer | Owner: was
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-5.13
Component: interfaces | Resolution:
Keywords: pari error interrupt | Merged in:
Authors: Peter Bruin | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
Dependencies: | Stopgaps:
----------------------------------------+----------------------------
Comment (by pbruin):
Replying to [comment:18 jdemeyer]:
> Replying to [comment:16 pbruin]:
> > Why `abort()` and not `raise(SIGUSR1)` or another signal code?
> Because we already handle `abort()` anyway and because I see no gain of
adding an extra signal, with the risk that `SIGUSR1` is used by other Sage
packages.
But we handle it by raising a new `RuntimeError`, among other things,
unless I misunderstand `interrupt.c`. So wouldn't the `SIGABRT` handler
need to have a special case for the case where it is called in this way?
This would be rather inelegant.
--
Ticket URL: <http://trac.sagemath.org/ticket/9640#comment:19>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/groups/opt_out.
