Permalink
Browse files

perlbeos: change some C<>'s into F<>'s

  • Loading branch information...
Karl Williamson
Karl Williamson committed Jul 16, 2011
1 parent 75b25ca commit 4daee454664fa55eb0388383fdc21b96e7eceb0b
Showing with 4 additions and 5 deletions.
  1. +4 −4 README.beos
  2. +0 −1 t/porting/known_pod_issues.dat
View
@@ -19,7 +19,7 @@ I have built and tested Perl 5.8.6 and 5.9.1 under BeOS R5 x86 net server.
I can't say anything with regard to PPC. Since Perl 5.8.0 had been released
for BeOS BONE, I suspect, there is a good chance, that it still compiles on
a BONE system. The only change I've made, that affects BONE systems is the
-recognition of whether it is a BONE system or not in C<hints/beos.sh>. Now
+recognition of whether it is a BONE system or not in F<hints/beos.sh>. Now
network socket support should remain enabled on BONE systems. This might
as well break the build, though.
@@ -81,21 +81,21 @@ to try enabling it and see what problems occur.
=item *
-The LFS (large file support) tests (C<t/op/lfs> and C<xt/Fcntl/t/syslfs>) are
+The LFS (large file support) tests (F<t/op/lfs> and F<xt/Fcntl/t/syslfs>) are
disabled as seeking beyond 2 GB is broken according to jhi@iki.fi who was the
last one checking the BeOS port and updating this file before me. Haven't
checked this myself.
=item *
-The C<t/io/fflush> test fails at #6. As far as I can tell, this is caused by
+The F<t/io/fflush> test fails at #6. As far as I can tell, this is caused by
a bug in the BeOS pipes implementation that occurs when starting other child
processes. In the particular test case a C<system("perl -e 0")> flushes the
stdout pipe of another child process.
=item *
-The C<ext/POSIX/t/waitpid> test fails at #1. After all child processes are
+The F<ext/POSIX/t/waitpid> test fails at #1. After all child processes are
gone BeOS' waitpid(-1,...) returns 0 instead of -1 (as it should). No idea
how to fix this.
@@ -214,7 +214,6 @@ pod/perlapi.pod ? Should you be using L<...> instead of 86
pod/perlapi.pod Verbatim line length including indents exceeds 80 by 23
pod/perlapi.pod unresolved internal link 3
pod/perlapio.pod Verbatim line length including indents exceeds 80 by 5
-pod/perlbeos.pod ? Should you be using F<...> or maybe L<...> instead of 5
pod/perlbook.pod Verbatim line length including indents exceeds 80 by 1
pod/perlcall.pod Verbatim line length including indents exceeds 80 by 2
pod/perlce.pod Verbatim line length including indents exceeds 80 by 2

0 comments on commit 4daee45

Please sign in to comment.