I'm taking the liberty of forwarding Brad's reply to the list. I figure others might be interested. Regards, Ben ----- Forwarded message from Bradley Lucier <lucier@math.purdue.edu> ----- Cc: Bradley Lucier <lucier@math.purdue.edu> From: Bradley Lucier <lucier@math.purdue.edu> Subject: Re: [gambit-list] Are faster bignums important? Date: Tue, 29 Mar 2005 23:07:05 -0500 To: ben@fuhok.net X-Mailer: Apple Mail (2.619.2) On Mar 29, 2005, at 10:22 PM, ben@fuhok.net wrote:

What's the downside? I'm all for increased performance of course. Fast code is one of the reasons that I'm interested in Gambit.

One downside is somewhat technical, but users can run into it. Marc can correct my naive interpretation of what's happening. Gambit manages its own interrupts; first it masks the ^C interrupt, and if you hit ^C while a gambit process is running, then Gambit only stops when it hits a POLL statement in the generated C code. POLL statements are put where the Gambit Virtual Machine (GVM) is in a known state, so the debugger will work, give a correct backtrace, etc. Any C code for the FFT will not have these POLL statements, so you will not be able to interrupt an FFT that could take several seconds (or minutes, for very large integers) to finish. You can pause it with ^Z and then kill it, but that's about it. Brad ----- End forwarded message -----