From: Alex Riesen <raa.lkml@gmail.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org, Junio C Hamano <junkio@cox.net>
Subject: Re: [PATCH] Add test-tr: poor-man tr
Date: Thu, 12 Jun 2008 08:01:52 +0200 [thread overview]
Message-ID: <20080612060152.GA3798@steel.home> (raw)
In-Reply-To: <20080611225448.GC19474@sigill.intra.peff.net>
Jeff King, Thu, Jun 12, 2008 00:54:48 +0200:
> On Wed, Jun 11, 2008 at 08:25:01PM +0200, Alex Riesen wrote:
>
> > It offers a limited set of POSIX tr, in particular: no character class
> > support and no [n*m] operators. Only 8bit. C-escapes supported, and
> > character ranges. Deletion and squeezing should work, but -s does not
> > match the GNU tr from coreutils (which, in turn, does not match POSIX).
> >
> > Signed-off-by: Alex Riesen <raa.lkml@gmail.com>
> > ---
> >
> > Rebased on top of current master. I still think it makes the test
> > suite more portable.
>
> Having wrestled with Solaris tr, I can understand where you are coming
> from. However, does this _actually_ increase the portability of the test
> suite? That is, are there failing tests that this fixes, and if so, for
> which platforms (getting a successful run of the test suite on Solaris
> is still on my long-term todo, but I thought I had fixed all of the tr
> issues)?
Frankly, it started because I wanted to minimize use of Perl on
Windows (because I can't get around ActiveState Perl at work, and it
breaks almost everything it touches). Accidentally, it is also faster
there (maybe just because it's smaller).
But, as was already noted, tr does not behave the same for all
platforms (there were even differences in output, BSD or Solaris put
out a stray LF?).
> Or is your rationale "this will prevent people from screwing up the test
> scripts accidentally in the future"?
We just can't have that. Nothing can prevent people from screwing up
anything in any given point of time :)
In any case, I wont push this change too hard. I must admit, that
there is no real good reason besides one "screwed" company using
obsoleted tools in a weird way. And it is a maintenance effort (and
people will forget to use test-tr instead of perl and tr).
And maybe someday my employment situation improves and I wont push it
at all :)
next prev parent reply other threads:[~2008-06-12 6:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-11 18:25 [PATCH] Add test-tr: poor-man tr Alex Riesen, Alex Riesen
2008-06-11 18:26 ` [PATCH] Use test-tr in the tests Alex Riesen
2008-06-11 21:34 ` [PATCH] Add test-tr: poor-man tr Alex Riesen
2008-06-11 22:54 ` Jeff King
2008-06-12 6:01 ` Alex Riesen [this message]
2008-06-12 6:23 ` Jeff King
2008-06-12 6:28 ` Jeff King
2008-06-12 20:32 ` Alex Riesen
2008-06-13 6:02 ` Jeff King
2008-06-13 17:26 ` Alex Riesen
2008-06-13 18:00 ` Jeff King
2008-06-12 6:32 ` Alf Clement
2008-06-12 7:25 ` Johannes Schindelin
2008-06-12 20:20 ` Alex Riesen, Alex Riesen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080612060152.GA3798@steel.home \
--to=raa.lkml@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=peff@peff.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).