Re: seq: fix check for rounding error/truncation

2023-06-12 Thread Todd C . Miller
On Mon, 12 Jun 2023 18:48:56 +0100, Stuart Henderson wrote: > Neither of these are really ideal, and mean that we still need gseq > for integers >= 1,000,000 > > $ seq 99 99 > 99 > $ seq 100 100 > 1e+06 > > $ gseq 105 105 > 105 That probably requires a separate cod

Re: seq: fix check for rounding error/truncation

2023-06-12 Thread Stuart Henderson
On 2023/06/12 11:20, Todd C. Miller wrote: > We need to compare the printable version of the last value displayed, > not the floating point representation. Otherwise, we may print the > last value twice. > > Old: > > $ seq 105 105 > 1.05e+06 > 1.05e+06 > > New: > > $ se

Re: seq: fix check for rounding error/truncation

2023-06-12 Thread Todd C . Miller
For context, see: https://chaos.social/@Gottox/110527807405964874 https://github.com/chimera-linux/chimerautils/commit/1ecc1e99d4a309631e846a868b5a422f996704ac

seq: fix check for rounding error/truncation

2023-06-12 Thread Todd C . Miller
We need to compare the printable version of the last value displayed, not the floating point representation. Otherwise, we may print the last value twice. Old: $ seq 105 105 1.05e+06 1.05e+06 New: $ seq 105 105 1.05e+06 We really need seq regression tests.