GNU bug report logs - #23110
seq apparent bug

Previous Next

Package: coreutils;

Reported by: Маренков Евгений <hotpil <at> mail.ru>

Date: Thu, 24 Mar 2016 17:23:03 UTC

Severity: normal

Tags: fixed

Done: Assaf Gordon <assafgordon <at> gmail.com>

Bug is archived. No further changes may be made.

Full log


Message #41 received at 23110 <at> debbugs.gnu.org (full text, mbox):

From: Paul Eggert <eggert <at> cs.ucla.edu>
To: Ruediger Meier <sweet_f_a <at> gmx.de>, 23110 <at> debbugs.gnu.org
Subject: Re: bug#23110: seq apparent bug
Date: Fri, 8 Apr 2016 15:21:17 -0700
On 04/08/2016 01:51 PM, Ruediger Meier wrote:
> On Friday 08 April 2016, Paul Eggert wrote:
>> For this I suggest the following heuristic. When inferring a format 
>> that would apply to two or more lines of output, try formatting the 
>> first two lines and report an error if they are the same. 
> Hm, I think printing identical lines is a valid use case:
> $ seq -f "%0.1f" 0 0.02 0.1
> 0.0
> 0.0
> 0.0
> 0.1
> 0.1
> 0.1

Sure, but the heuristic I suggested was for inferred formats only. It 
was not intended for formats explicitly specified via -f.

> I would check it before the loop like this
>
> if ((first + inc) == first)
> 	/* exit error */

I think I'd prefer testing what the user would see, instead of testing 
some internal variable.

> maybe the user _wants_ an effective endless (non
> trivial) sequence

If we make an increment of zero an error, then there's no way for the 
'seq' user to say they want an endless identical sequence. But there's 
always the 'yes' program for that.





This bug report was last modified 6 years and 210 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.