>> That the program crashes is the result of poor coding practice. A
>> single comparison operation in the subroutine which allocates a bignum
>> can signal an informative exception with plenty of main memory
>> available for the debugger.
> The question then becomes, what "coding practice" do we want to force on
> (and explain to) new users of scheme and what kind of errors do we want
> them to have to deal with (and understand) when they fail to do so?
I think the O.P. meant coding practice in the Scheme implementation itself,
not by users.
The point is that there's an interesting useful range of bignums much smaller
than the size of memory, but much bigger than 2^31.
But what gives /me/ the heebie-jeebies is having to have a .schemerc file
full of things like
(set! fixnum-overflow-mode 'bignum)
(set! lg-of max-bignum 400)
or whatever.
_______________________________________________
r6rs-discuss mailing list
[email protected]
http://lists.r6rs.org/cgi-bin/mailman/listinfo/r6rs-discuss
