Permalink
Browse files

Fix POD syntax in bytecode.pod

I'm not used to writing POD, and I used =cut where I should have used
=back
  • Loading branch information...
1 parent f74f55f commit 7769a3651fc5f72025878d5eb37405535d99b9c5 @Benabik Benabik committed Aug 20, 2011
Showing with 4 additions and 2 deletions.
  1. +4 −2 docs/pct/bytecode.pod
View
@@ -58,7 +58,7 @@ returns the main method from the source for execution by the compiler.
Using C<--output file.pbc> will allow you to save the generated packfile to
a file.
-=cut
+=back
=head1 KNOWN ISSUES
@@ -78,7 +78,7 @@ Because PIR is not generated when using these stages, inline PIR can not be
used. To add this, a more fine-grained PIR parser would need to be addthat
outputs newPOST trees.
-=cut
+=back
=head1 UNKNOWN ISSUES
@@ -95,4 +95,6 @@ This likely means that some portion of PIR text made its way into
C<POST::PBCCompiler>. An additional override in C<PAST::NewCompiler> will
probably be needed to replace/alter the generated POST tree.
+=back
+
=cut

0 comments on commit 7769a36

Please sign in to comment.