max-int Bradley Lucier (25 Jan 2024 21:40 UTC)
Re: max-int John Cowan (26 Jan 2024 05:28 UTC)
Re: max-int Bradley Lucier (26 Jan 2024 14:23 UTC)
(missing)
Re: max-int Bradley Lucier (26 Jan 2024 16:30 UTC)
Re: max-int Marc Feeley (26 Jan 2024 17:42 UTC)
Re: max-int John Cowan (26 Jan 2024 22:10 UTC)
Re: max-int Bradley Lucier (27 Jan 2024 01:00 UTC)
Re: max-int Shiro Kawai (27 Jan 2024 08:39 UTC)
Re: max-int Antero Mejr (27 Jan 2024 21:29 UTC)

Re: max-int Bradley Lucier 26 Jan 2024 14:23 UTC

On 1/26/24 12:27 AM, John Cowan wrote:
> The disadvantage of this idea is that it would fail to test bignums at all.

The current definition

     (define max-int 1000000000000000001)

fails to test any bignums at all on 64-bit Gambit, because
1000000000000000001 is a fixnum.

When I set about testing SRFI 231, I had a switch to generate fixnum
bounds or bignum bounds for intervals.

So perhaps there should be a fixnum generator and a bignum generator as
well as an integer generator.

max-int is used in a lot of places in the code, I don't know how much of
a change this would be.  Presumably you wouldn't need ratios with bignum
numerators and denominators, bignums converted to flonums, etc.

Brad