The main reason I recommended not to use that function in time critical stuff is it is very, very slow (for reasons I don't understand).
The talk was about writing highly time critical code. The best way around that is to roll your own, which can often be made much faster. Bill. 2009/5/23 William Stein <[email protected]>: > > On Fri, May 22, 2009 at 7:13 PM, Case Vanhorsen <[email protected]> wrote: >> >> On Wed, May 20, 2009 at 8:29 PM, Bill Hart <[email protected]> >> wrote: >>> >>> Today at Sage Days 15 in Seattle, I gave a talk on MPIR. >>> >>> I've been experimenting with the Sage notebook, which is very capable, >>> but I am no, hence the (somewhat broken) notes from my talk are >>> available here: >>> >>> http://www.sagenb.org/home/pub/558/ >>> >>> Developers may find some of the notes useful, though a couple of >>> errors have already been pointed out to me. >> That link no longer works but when I skimmed it early it recommended >> to never use mpz_import and mpz_export. Is there a particular reason? >> (I use both functions in gmpy to convert between the internal >> representation of a Python longint and an mpz.) >> > > You can get the sage worksheet or pdf of the talk from this wiki page: > > http://wiki.sagemath.org/days15 > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
