On 2010-09-04 00:05, Bill Hart wrote: > Regarding the internal undocumented functions used by Pari, if there > are no missing symbol errors when you build against MPIR, then it is > likely these are mpn functions that were formerly undocumented, but > now part of the documented interface. I think it would be safe to > leave that flag set (so long as it actually compiles and links).
PARI doesn't use any undocumented functions, it uses the structure of the mpz_t type (see MPIR documentation, section 16.1). It would be useful for PARI (and hence Sage) to have a public interface for mpn_divexact (currently, there is only mpn_divexact_by3 and mpn_divexact_by3c). Jeroen. -- You received this message because you are subscribed to the Google Groups "mpir-devel" 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/mpir-devel?hl=en.
