Re: t6044 broken on pu
- From
Jeff King <peff@peff.net>
- Date
- May 9, 2016, 08:33 UTC
- Message-ID
- <20160509083323.GB14299@sigill.intra.peff.net>
- In-Reply-To
- <CANgJU+V9+-hTFvDxCGbQxFcHMRcFaP-NdS_P93DqXuxi1Lh4mg@mail.gmail.com>
On Mon, May 09, 2016 at 08:30:51AM +0200, demerphq wrote:
Show 17 quoted lines
> > - perl -le 'print for $ARGV[0]..$ARGV[1]' -- "$@" > > + test_seq_counter__=$1 > > + while test "$test_seq_counter__" -le $2 > > + do > > + echo "$test_seq_counter__" > > + test_seq_counter__=$((test_seq_counter__ + 1)) > > + done > > } > > Is that perl snippet ever called with non-numeric output? > > perl -le 'print for $ARGV[0]..$ARGV[1]' -- A E > A > B > C > D > E
I had that thought, too, but I think it would be an error to do so. test_seq is supposed to be a replacement for "seq", which does not understand non-numeric sequences.
A quick "git grep test_seq" seems to back that up.
-Peff