#13447: Make libsingular multivariate polynomial rings collectable
----------------------------------------------------------------+-----------
Reporter: nbruin |
Owner:
Type: defect |
Status: needs_work
Priority: major |
Milestone: sage-5.4
Component: memleak |
Resolution:
Keywords: | Work
issues: Understand why sometimes `new_RingWrap` needs an incref and sometimes
not
Report Upstream: None of the above - read trac for reasoning. |
Reviewers: Simon King
Authors: Nils Bruin, Simon King | Merged
in:
Dependencies: #11521 |
Stopgaps:
----------------------------------------------------------------+-----------
Comment (by SimonKing):
Here is one complication for singular_function: If you do
`singular_function("std")`, then a `SingularKernelFunction` is created. In
its `__init__`, it creates a call handler, and for that purpose it needs
to find out the arity of the Singular kernel function.
But apparently the arity of std can not be correctly determined, if
`currRing==0`: One obtains arity 0, not 1, for std.
Therefore, when I move the creation of `currRingHdl` from
`SingularFunction.__init__` to where the function is called, an error
occurs.
A question arises: Is there a singular function that changes its arity
depending on `currRing`? If it is the case, then we must determine
`SingularKernelFunction.call_handler` each time the function is called,
rather than during initialisation.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13447#comment:71>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
