is(1, 1, "RT #124207");
# RT #127993 version control conflict markers
+my @conflict_markers = map { $_ x 7 } qw( < = > );
" this should keep working
-<<<<<<<
+$conflict_markers[0]
" =~ /
->>>>>>>
+$conflict_markers[2]
/;
-for my $marker (qw(
-<<<<<<<
-=======
->>>>>>>
-)) {
+for my $marker (@conflict_markers) {
eval "$marker";
like $@, qr/^Version control conflict marker at \(eval \d+\) line 1, near "$marker"/, "VCS marker '$marker' at beginning";
eval "\$_\n$marker";
EXPECT
Illegal declaration of subroutine BEGIN at - line 1.
########
-# NAME multiple conflict markers
-<<<<<<< yours:sample.txt
+# NAME multiple conflict markers.
+# NOTE the <CONFLICT< style text is auto-replaced in test.pl run_multiple_progs
+<CONFLICT< yours:sample.txt
my $some_code;
-=======
+=CONFLICT=
my $some_other_code;
->>>>>>> theirs:sample.txt
+>CONFLICT> theirs:sample.txt
EXPECT
-Version control conflict marker at - line 1, near "<<<<<<<"
-Version control conflict marker at - line 3, near "======="
-Version control conflict marker at - line 5, near ">>>>>>>"
+Version control conflict marker at - line 1, near "<CONFLICT<"
+Version control conflict marker at - line 3, near "=CONFLICT="
+Version control conflict marker at - line 5, near ">CONFLICT>"
Execution of - aborted due to compilation errors.
########
# NAME (Might be a runaway multi-line...) with Latin-1 delimiters in utf8
if (s/^(\s*-\w+)//) {
$switch = $1;
}
+
+ s/^# NOTE.*\n//mg; # remove any NOTE comments in the content
+
+ # unhide conflict markers - we hide them so that naive
+ # conflict marker detection logic doesn't get upset with our
+ # tests.
+ s/([<=>])CONFLICT\1/$1 x 7/ge;
+
my ($prog, $expected) = split(/\nEXPECT(?:\n|$)/, $_, 2);
my %reason;