From 56466d0ead41a249b0feba363954f09c4f090035 Mon Sep 17 00:00:00 2001 From: Nicholas Clark Date: Wed, 22 Jun 2011 11:56:50 +0200 Subject: [PATCH] The podchecker much prefers a forward slash in F It looks for the file within the F<> - on *nix, 'symbian\TODO' doesn't exist, so the line is flagged as a known issue. On Windows, it does exist (because at the API level, / and \ are both valid as directory separators), so there is no known issue, and the test fails with a request to delete the known issue. README.symbian is not consistent in its use of backward or forward slashes inside F<> markup, so this isn't the first use of a forward slash. (The podchecker has other exemption rules for F<>, hence why this doesn't matter in some cases.) --- README.symbian | 2 +- t/porting/known_pod_issues.dat | 1 - 2 files changed, 1 insertion(+), 2 deletions(-) diff --git a/README.symbian b/README.symbian index 04678fe..3be86ae 100644 --- a/README.symbian +++ b/README.symbian @@ -301,7 +301,7 @@ the Perl definitions and redefines them as PerlNew() and PerlCopy(). =head1 TO DO -Lots. See F. +Lots. See F. =head1 WARNING diff --git a/t/porting/known_pod_issues.dat b/t/porting/known_pod_issues.dat index 7106386..e0b9e57 100644 --- a/t/porting/known_pod_issues.dat +++ b/t/porting/known_pod_issues.dat @@ -283,7 +283,6 @@ pod/perlsolaris.pod Verbatim line length including indents exceeds 80 by 14 pod/perlsource.pod ? Should you be using F<...> or maybe L<...> instead of 1 pod/perlsub.pod ? Should you be using F<...> or maybe L<...> instead of 3 pod/perlsub.pod Verbatim line length including indents exceeds 80 by 4 -pod/perlsymbian.pod ? Should you be using L<...> instead of 1 pod/perlsymbian.pod Verbatim line length including indents exceeds 80 by 20 pod/perlsyn.pod Verbatim line length including indents exceeds 80 by 7 pod/perlthrtut.pod Verbatim line length including indents exceeds 80 by 5 -- 2.7.4