Closed p5pRT closed 18 years ago
Gentlemen\, would you look at that. Perldoc is ignoring additional arguments without any qualms: $ perldoc -f no-op noop No documentation for perl function `no-op' found $ perldoc -q no-op noop No documentation for perl FAQ keyword `no-op' found
However it is acceptable here:
$ perldoc perldoc perlop Perldoc is only really meant for reading one document at a time. So these parameters are being ignored: /usr/share/perl/5.8/pod/perlop.pod
[jidanni@jidanni.org - Wed Aug 18 15:59:12 2004]:
Gentlemen\, would you look at that. Perldoc is ignoring additional arguments without any qualms: $ perldoc -f no-op noop No documentation for perl function `no-op' found $ perldoc -q no-op noop No documentation for perl FAQ keyword `no-op' found
However it is acceptable here:
$ perldoc perldoc perlop Perldoc is only really meant for reading one document at a time. So these parameters are being ignored: /usr/share/perl/5.8/pod/perlop.pod
Attached is patch for this behaviour.
Robin
The RT System itself - Status changed from 'new' to 'open'
[jidanni@jidanni.org - Wed Aug 18 15:59:12 2004]:
Gentlemen\, would you look at that. Perldoc is ignoring additional arguments without any qualms: $ perldoc -f no-op noop No documentation for perl function `no-op' found $ perldoc -q no-op noop No documentation for perl FAQ keyword `no-op' found
However it is acceptable here:
$ perldoc perldoc perlop Perldoc is only really meant for reading one document at a time. So these parameters are being ignored: /usr/share/perl/5.8/pod/perlop.pod
$ perldoc -h perldoc [options] PageName|ModuleName|ProgramName... perldoc [options] -f BuiltinFunction perldoc [options] -q FAQRegex
Typically\, if more than one input parameter can be used\, "..." is used to show that this is allowed. This is not the case with perldoc -f or -x. Adding code to trap something that is undocumented seems like overkill to me.
@smpeters - Status changed from 'open' to 'rejected'
On Fri\, Oct 22\, 2004 at 06:00:40PM -0000\, Steve Peters via RT wrote:
$ perldoc -h perldoc [options] PageName|ModuleName|ProgramName... perldoc [options] -f BuiltinFunction perldoc [options] -q FAQRegex
Typically\, if more than one input parameter can be used\, "..." is used to show that this is allowed. This is not the case with perldoc -f or -x. Adding code to trap something that is undocumented seems like overkill to me.
Garbage in\, garbage out. Bad. Garbage in\, nothing out. Less bad. Garbage in\, error out. Good.
perldoc -f should check its arguments.
-- Michael G Schwern schwern@pobox.com http://www.pobox.com/~schwern/ Cottleston\, Cottleston\, Cottleston Pie. Why does a chicken\, I don't know why. Ask me a riddle and I reply: "Cottleston\, Cottleston\, Cottleston Pie."
@smpeters - Status changed from 'rejected' to 'open'
I supplied a patch for this (on rt.perl.org). I suggest it should go in 5.8.6
Robin
-----Original Message----- From: Michael G Schwern [mailto:schwern@pobox.com] Sent: 22 October 2004 19:35 To: Steve Peters via RT Cc: perl5-porters@perl.org Subject: Re: [perl #31227] perldoc -f\, -q ignores extra arguments with no notice
On Fri\, Oct 22\, 2004 at 06:00:40PM -0000\, Steve Peters via RT wrote:
$ perldoc -h perldoc [options] PageName|ModuleName|ProgramName... perldoc [options] -f BuiltinFunction perldoc [options] -q FAQRegex
Typically\, if more than one input parameter can be used\, "..." is used to show that this is allowed. This is not the case with perldoc -f or -x. Adding code to trap something that is undocumented seems like overkill to me.
Garbage in\, garbage out. Bad. Garbage in\, nothing out. Less bad. Garbage in\, error out. Good.
perldoc -f should check its arguments.
-- Michael G Schwern schwern@pobox.com http://www.pobox.com/~schwern/ Cottleston\, Cottleston\, Cottleston Pie. Why does a chicken\, I don't know why. Ask me a riddle and I reply: "Cottleston\, Cottleston\, Cottleston Pie."
This e-mail and any attachments may contain confidential and/or privileged material; it is for the intended addressee(s) only. If you are not a named addressee\, you must not use\, retain or disclose such information.
NPL Management Ltd cannot guarantee that the e-mail or any attachments are free from viruses.
NPL Management Ltd. Registered in England and Wales. No: 2937881 Registered Office: Teddington\, Middlesex\, United Kingdom TW11 0LW.
[jidanni@jidanni.org - Wed Aug 18 15:59:12 2004]:
Gentlemen\, would you look at that. Perldoc is ignoring additional arguments without any qualms: $ perldoc -f no-op noop No documentation for perl function `no-op' found $ perldoc -q no-op noop No documentation for perl FAQ keyword `no-op' found
However it is acceptable here:
$ perldoc perldoc perlop Perldoc is only really meant for reading one document at a time. So these parameters are being ignored: /usr/share/perl/5.8/pod/perlop.pod
The patch has been provided to the Pod-Perldoc rt.cpan.org queue at https://rt.cpan.org/ NoAuth/Bug.html?id=11310
[rmb1 - Mon Sep 20 11:57:47 2004]:
[jidanni@jidanni.org - Wed Aug 18 15:59:12 2004]:
Gentlemen\, would you look at that. Perldoc is ignoring additional arguments without any qualms: $ perldoc -f no-op noop No documentation for perl function `no-op' found $ perldoc -q no-op noop No documentation for perl FAQ keyword `no-op' found
However it is acceptable here:
$ perldoc perldoc perlop Perldoc is only really meant for reading one document at a time. So these parameters are being ignored: /usr/share/perl/5.8/pod/perlop.pod
Attached is patch for this behaviour.
Robin
The attached patch was applied as change #27878.
@smpeters - Status changed from 'open' to 'resolved'
Migrated from rt.perl.org#31227 (status was 'resolved')
Searchable as RT31227$