#9964: Document _pari_ and _pari_init_
-----------------------------+----------------------------------------------
Reporter: jdemeyer | Owner: mvngu
Type: defect | Status: new
Priority: blocker | Milestone: sage-4.6
Component: documentation | Keywords:
Author: | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
-----------------------------+----------------------------------------------
Comment(by mhansen):
Replying to [comment:5 jdemeyer]:
> I was a little too fast. If an object has a `_pari_` method and a
`_pari_init_` method, the `_pari_` method takes precedence, right? So it
doesn't hurt to have both (where `_pari_init` is then only used for Gp).
Yes, _pari_ takes precedence over _pari_init_. _pari_init_ is only used
in the default implmentation of _pari_.
SageObject provides default implementations of _gp_ and _gp_init_, and
most things are subclasses of SageObject.
I would be surprised if there weren't objects that used strings to
construct objects in the PARI C library interface since it is the default
implementation of !{{{pari(foo)}}}.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9964#comment:7>
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.
