#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:                 |  
-----------------------------+----------------------------------------------
Description changed by jdemeyer:

Old description:

> Many Sage objects have {{{_pari_}}} and/or {{{_pari_init_}}} member
> functions. However, it is not at all documented how these are supposed to
> work. Reading the source code gives some hints, but leaves some things
> unexplained, for example:
>  * what exactly is the interaction between {{{_pari_}}} and
> {{{_pari_init_}}}. Which of these two functions (or both) should be
> implemented?
>  * Why is {{{_pari_init_}}} also used for the GP interpreter {{{Gp}}}?
>  * Why must {{{_pari_init_}}} return a string? Is it only because it is
> also used for the GP interpreter or is there a deeper reason?

New description:

 Many Sage objects have {{{_pari_}}} and/or {{{_pari_init_}}} member
 functions. However, it is not at all documented how these are supposed to
 work. Reading the source code gives some hints, but leaves some things
 unexplained, for example:
  * what exactly is the interaction between {{{_pari_}}} and
 {{{_pari_init_}}}. Which of these two functions (or both) should be
 implemented?
  * Why is {{{_pari_init_}}} also used for the GP interpreter {{{Gp}}}?
  * Why must {{{_pari_init_}}} return a string? Is it only because it is
 also used for the GP interpreter or is there a deeper reason?

 Note also that the patch at #9400 contains important changes to a
 {{{_pari_init_}}} function which are completely not understood by the
 author.

--

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9964#comment:1>
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.

Reply via email to