From 4daee454664fa55eb0388383fdc21b96e7eceb0b Mon Sep 17 00:00:00 2001 From: Karl Williamson Date: Sat, 16 Jul 2011 12:43:28 -0600 Subject: [PATCH] perlbeos: change some C<>'s into F<>'s --- README.beos | 8 ++++---- t/porting/known_pod_issues.dat | 1 - 2 files changed, 4 insertions(+), 5 deletions(-) diff --git a/README.beos b/README.beos index 38bd581..c72c229 100644 --- a/README.beos +++ b/README.beos @@ -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. Now +recognition of whether it is a BONE system or not in F. 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 and C) are +The LFS (large file support) tests (F and F) 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 test fails at #6. As far as I can tell, this is caused by +The F 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 flushes the stdout pipe of another child process. =item * -The C test fails at #1. After all child processes are +The F 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. diff --git a/t/porting/known_pod_issues.dat b/t/porting/known_pod_issues.dat index 85e40db..029c870 100644 --- a/t/porting/known_pod_issues.dat +++ b/t/porting/known_pod_issues.dat @@ -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 -- 2.7.4