New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix readline docs in perlfunc #16874
Comments
From m@japh.seCreated by m@japh.seThe wording was a bit off in the readline docs in perlfunc. Perl Info
|
From m@japh.se0001-fix-readline-pod-error.patchFrom 8764c58140303b635abdddbc8f952392ff4efcdf Mon Sep 17 00:00:00 2001
From: Magnus Woldrich <m@japh.se>
Date: Wed, 6 Mar 2019 07:26:29 +0100
Subject: [PATCH] fix readline pod error
---
cpan/Pod-Perldoc/corpus/perlfunc.pod | 2 +-
pod/perlfunc.pod | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/cpan/Pod-Perldoc/corpus/perlfunc.pod b/cpan/Pod-Perldoc/corpus/perlfunc.pod
index 604123daf8..83e9a55468 100644
--- a/cpan/Pod-Perldoc/corpus/perlfunc.pod
+++ b/cpan/Pod-Perldoc/corpus/perlfunc.pod
@@ -4970,7 +4970,7 @@ C<readline> and dies if the result is not defined.
...
}
-Note that you have can't handle C<readline> errors that way with the
+Note that you can't handle C<readline> errors that way with the
C<ARGV> filehandle. In that case, you have to open each element of
C<@ARGV> yourself since C<eof> handles C<ARGV> differently.
diff --git a/pod/perlfunc.pod b/pod/perlfunc.pod
index 973a2612d7..2a24f2fc39 100644
--- a/pod/perlfunc.pod
+++ b/pod/perlfunc.pod
@@ -6219,7 +6219,7 @@ if the result is not defined.
...
}
-Note that you have can't handle L<C<readline>|/readline EXPR> errors
+Note that you can't handle L<C<readline>|/readline EXPR> errors
that way with the C<ARGV> filehandle. In that case, you have to open
each element of L<C<@ARGV>|perlvar/@ARGV> yourself since
L<C<eof>|/eof FILEHANDLE> handles C<ARGV> differently.
--
2.20.1
|
From @jkeenanOn Wed, 06 Mar 2019 06:34:30 GMT, m@japh.se wrote:
The correction to pod/perlfunc.pod looks good. The Pod-Perldoc distribution, however, is maintained upstream on CPAN, so any correction to cpan/Pod-Perldoc/corpus/*.pod ought to go upstream first (https://rt.cpan.org//Dist/Display.html?Queue=Pod-Perldoc). Of course, the 'corpus' exists mainly for the upstream distribution to have representative POD to chew on. It's not documentation per se. List: Do we have any SOP on how to handle this? Thank you very much. |
The RT System itself - Status changed from 'new' to 'open' |
The patch affecting Perl has now been applied as f992105. The remainder could be submitted upstream, but as Jim said, that text could just as well be gibberish, as it is for testing only. So there isn't much point to correcting it. Hence, I'm closing this ticket |
Migrated from rt.perl.org#133901 (status was 'open')
Searchable as RT133901$
The text was updated successfully, but these errors were encountered: