Closed p5pRT closed 20 years ago
The banners (at least the ones I've noticed) on my 5.6.0 man pages say
23/Mar/2000 perl 5.005\, patch 03 1
when I read them with perldoc.
I wonder if this is occurring because somewhere in the chain of subprograms being run by perldoc\, the wrong perl is being called. My feeling has always been that the various perl utilities should use the perl that is running them (via Config presumably)\, not one that might be found somewhere in the path. Same for calling other perl utilities.
I'm invoking the correct perl and perldoc at the start:
/usr/local/devel/perl-longlong/bin/perldoc perl
or
/usr/local/devel/perl-longlong/bin/perldoc pod/perl.pod
I'm not quite sure where it's going awry.
-joseph
"Joseph N. Hall" \joseph@​dixie\.cscaper\.com wrote
The banners (at least the ones I've noticed) on my 5.6.0 man pages say
23/Mar/2000 perl 5.005\, patch 03 1
when I read them with perldoc.
I wonder if this is occurring because somewhere in the chain of subprograms being run by perldoc\, the wrong perl is being called.
Not quite - actually it's calling the wrong version of pod2man. So you'll find it makes a right mess of\, e.g. "perldoc -f open" because it doesn't know about those new-fangled C\<\< ... >> thingies.
Patch (for 5.6.0) attached. Since it drags in File::Spec\, I also took the opportunity of eliminating the various /-is-the-dir-separator assumptions.
Mike Guy
Test message - please ignore
"M.J.T. Guy" wrote:
Test message - please ignore a reply from me this time
Migrated from rt.perl.org#2905 (status was 'resolved')
Searchable as RT2905$