From: Jeff King <peff@peff.net>
To: Christian Couder <christian.couder@gmail.com>
Cc: git <git@vger.kernel.org>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Junio C Hamano <gitster@pobox.com>
Subject: Re: t9700-perl-git.sh is broken on some configurations
Date: Fri, 4 Mar 2016 06:45:42 -0500 [thread overview]
Message-ID: <20160304114542.GB569@sigill.intra.peff.net> (raw)
In-Reply-To: <CAP8UFD3jZ2b8jgw8dR0U=AkPTTm5nO1F92UVjyeAMsfiOaJ_5w@mail.gmail.com>
On Fri, Mar 04, 2016 at 11:30:36AM +0100, Christian Couder wrote:
> > Those are just guesses, but if we are tickling a bug in perl's parser,
> > this might avoid them. I also wondered when "/r" appeared. It was in
> > 5.14, so you're presumably good there.
>
> If I just remove the "r" at the end of "s/\\/\//gr", I get with both
> Perl versions:
>
> Can't modify non-lvalue subroutine call at t/t9700/test.pl line 36.
Right, because the string being operated on is the return value of a
function, so we can't do substitution on it (unless with "r", whose
purpose is to allow exactly such a thing).
> > The "use" statement at the top of
> > the script says "5.008", so perhaps we should be writing it out longhand
> > anyway (that version is "only" 5 years old, so I suspect there are still
> > systems around with 5.12 or older).
>
> Yeah, it would work.
Thanks for confirming the longhand does work; I think the patch I just
posted elsewhere in the thread should be good for you, then.
-Peff
next prev parent reply other threads:[~2016-03-04 11:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-04 8:13 t9700-perl-git.sh is broken on some configurations Christian Couder
2016-03-04 8:56 ` Jeff King
2016-03-04 10:30 ` Christian Couder
2016-03-04 11:45 ` Jeff King [this message]
2016-03-04 10:58 ` Dennis Kaarsemaker
2016-03-04 11:43 ` [PATCH] t9700: fix test for perl older than 5.14 Jeff King
2016-03-04 12:21 ` Dennis Kaarsemaker
2016-03-04 20:12 ` Christian Couder
2016-03-04 16:21 ` Johannes Schindelin
2016-03-04 18:15 ` Junio C Hamano
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=20160304114542.GB569@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).