From: Nathan F. <fr...@ro...> - 2001-10-09 23:04:24
|
Ben Pharr - Lists wrote: > So what you're trying to say is that it's a big number? :-) Just > kidding. I knew it was a large number, but I wasn't quite grasping HOW > big. Thanks for explaining that to me. > > I'm still not sure why it overflows without eating up more than 1.1% of > my memory. Can anyone explain that to me? I realize it doesn't matter in > this particular situation, but it might in the future. It's possible (not being an expert on CLISP internals) that the bignum code inside of CLISP is smart enough to recognize when you give it operands that are far larger than it can ever hope to operate on. So A(4,2) calculates quickly, is really huge, and it overflows some internal limit. -Nathan |