Skip to content
Browse files

Remove pieces of invalid Pod

  • Loading branch information...
1 parent 0058a89 commit efd5f2155e4fadf4c0a80d5b0c773a6f1574bfe9 @tadzik tadzik committed May 22, 2011
Showing with 11 additions and 10 deletions.
  1. +4 −4 S02-whitespace_and_comments/unspace.t
  2. +2 −2 S03-metaops/hyper.t
  3. +3 −2 S03-operators/binding-scalars.t
  4. +2 −2 S03-smartmatch/disorganized.t
View
8 S02-whitespace_and_comments/unspace.t
@@ -122,15 +122,15 @@ is(eval('foo\
#?rakudo todo 'pod and unspace'
is(eval('foo\
=\
-=begin nested pod
+=begin nested_pod
blah blah blah
-=end nested pod
+=end nested_pod
begin comment
blah blah blah
=\
-=begin nested pod
+=begin nested_pod
blah blah blah
-=end nested pod
+=end nested_pod
end comment
.lc'), 'a', 'unspace with pod =begin/=end comment w/ pod-in-pod');
#?rakudo skip '=for pod not implemented (in STD.pm)'
View
4 S03-metaops/hyper.t
@@ -346,7 +346,7 @@ my @e;
# mixed hyper and reduce metaops -
# this unveils a spec bug as << recurses into arrays and [+] never gets applied,
# so we disable the entire chunk for now.
-=begin todo unspecced
+=begin todo_unspecced
is ~([+]<< ([1,2,3], [4,5,6])), "6 15", "mixed hyper and reduce metaop ([+]<<) works";
## XXX: Test for [+]<<<< - This is unspecced, commenting it out
@@ -356,7 +356,7 @@ my @e;
is ~([+]« [1,2,3], [4,5,6]), "6 15",
"mixed Unicode hyper and reduce metaop ([+]«) works";
-=end todo unspecced
+=end todo_unspecced
#?pugs todo 'hyper ops'
{ # hyper dereferencing
View
5 S03-operators/binding-scalars.t
@@ -2,13 +2,14 @@ use v6;
use Test;
-=begin head1 Binding tests
+=begin head1
+Binding tests
These tests are derived from the "Item assignment precedence" section of Synopsis 3
# L<S03/Item assignment precedence/replaces the container itself For instance>
-=end head1 Binding tests
+=end head1
plan 29;
View
4 S03-smartmatch/disorganized.t
@@ -48,14 +48,14 @@ sub eval_elsewhere($code){ eval($code) }
# reviewed by moritz on 2009-07-07 up to here.
-=begin begin Explanation
+=begin Explanation
You may be wondering what the heck is with all these try blocks.
Prior to r12503, this test caused a horrible death of Pugs which
magically went away when used inside an eval. So the try blocks
caught that case.
-=end begin Explanation
+=end Explanation
{
my $result = 0;

0 comments on commit efd5f21

Please sign in to comment.
Something went wrong with that request. Please try again.