summaryrefslogtreecommitdiff
path: root/t/re
diff options
context:
space:
mode:
authorDagfinn Ilmari Mannsåker <ilmari@ilmari.org>2020-04-23 14:33:05 +0100
committerDagfinn Ilmari Mannsåker <ilmari@ilmari.org>2020-05-22 10:45:06 +0100
commita3815e44b8fba04704944693e426f3f47362d3ff (patch)
tree6b3f332bf90d50e6d3c8320ad29a05b83ae5aef0 /t/re
parent49704e1a7f79e12814aa5fa55084f1105e2b27ec (diff)
downloadperl-a3815e44b8fba04704944693e426f3f47362d3ff.tar.gz
Fix a bunch of repeated-word typos
Mostly in comments and docs, but some in diagnostic messages and one case of 'or die die'.
Diffstat (limited to 't/re')
-rw-r--r--t/re/pat_re_eval.t8
-rw-r--r--t/re/recompile.t2
2 files changed, 5 insertions, 5 deletions
diff --git a/t/re/pat_re_eval.t b/t/re/pat_re_eval.t
index 696b6a3fb5..75c6ed6306 100644
--- a/t/re/pat_re_eval.t
+++ b/t/re/pat_re_eval.t
@@ -1281,7 +1281,7 @@ sub run_tests {
# RT #132772
#
# Ensure that optimisation of OP_CONST into OP_MULTICONCAT doesn't
- # leave any freed ops in the execution path. This is is associated
+ # leave any freed ops in the execution path. This is associated
# with rpeep() being called before optimize_optree(), which causes
# gv/rv2sv to be prematurely optimised into gvsv, confusing
# S_maybe_multiconcat when it tries to reorganise a concat subtree
@@ -1294,11 +1294,11 @@ sub run_tests {
ok /^a(??{ $b."c" })$/, "RT #132772 - compile time";
ok /^$a(??{ $b."c" })$/, "RT #132772 - run time";
my $qr = qr/^a(??{ $b."c" })$/;
- ok /$qr/, "RT #132772 - compile time time qr//";
+ ok /$qr/, "RT #132772 - compile time qr//";
$qr = qr/(??{ $b."c" })$/;
- ok /^a$qr$/, "RT #132772 - compile time time qr// compound";
+ ok /^a$qr$/, "RT #132772 - compile time qr// compound";
$qr = qr/$a(??{ $b."c" })$/;
- ok /^$qr$/, "RT #132772 - run time time qr//";
+ ok /^$qr$/, "RT #132772 - run time qr//";
}
# RT #133687
diff --git a/t/re/recompile.t b/t/re/recompile.t
index 8c9b92e126..5a6f7d7f91 100644
--- a/t/re/recompile.t
+++ b/t/re/recompile.t
@@ -147,7 +147,7 @@ comp_n(3, <<'CODE', 'mixed utf8 qr');
"a" =~ qr/$_/ for "\x{c4}\x{80}", "\x{100}", "\x{c4}\x{80}";
CODE
-# note that that for runtime code, each pattern is compiled twice; the
+# note that for runtime code, each pattern is compiled twice; the
# second time to allow the parser to see the code.
comp_n(6, <<'CODE', 'runtime code');