[COMMIT] Have NATNUMP give t for positive bignums; check limits appropriately.

This is annoyingly invasive, and doesn’t lead to any real benefit for users, just for programmers. It still should go in, though. The issue is that NATNUMP() currently gives zero for positive bignums, while #'natnump gives one. So there are many places where you get errors that look like (wrong-type-argument natnump <some big positive number>); this changes many of them to give range errors instead. In other places it is appropriate to accept a bignum of the appropriate size, e.g. in #'accept-process-output for the timer arguments, where a fixnum does not have enough precision. # HG changeset patch # User Aidan Kehoe <kehoea(a)parhasard.net&gt; # Date 1290271751 0 # Node ID c096d8051f893c2a283f1c7f306a8340e470ed45 # Parent cde1608596d0b70c29939d8f4701299c3cf4aa1e Have NATNUMP give t for positive bignums; check limits appropriately.