Skip Menu |

This queue is for tickets about the Pod-Parser CPAN distribution.

Report information
The Basics
Id: 38245
Status: resolved
Priority: 0/
Queue: Pod-Parser

People
Owner: Nobody in particular
Requestors: plm [...] netspace.net.au
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: Pod::Usage( -verbose => 1 ) producing no output
Date: Wed, 06 Aug 2008 22:37:33 +1000
To: bug-Pod-Parser [...] rt.cpan.org
From: Paul Matthews <plm [...] netspace.net.au>
The machine in question is OpenSuSE 10.3 running perl 5.8.8. The version of Pod::Usage is 1.33. The same happens at work on our (newish) Solaris machines. The program below works fine if given the option --manual, it prints the manual page. It produces to expected output if given an illegal option (say --foo). But when asked for --help it produces no output at all ! I've run out of clues. Help please. plm@thunk:~/work/prj/bin> ./podme --foo Unknown option: foo Usage: program ( --help | -- manual ) plm@thunk:~/work/xde/bin> ./podme --help plm@thunk:~/work/xde/bin> cat ./podme #!/usr/bin/perl -w use Getopt::Long; use Pod::Usage; use strict; my $help; my $manual; GetOptions( 'help' => \$help, 'manual' => \$manual ) || pod2usage(2); pod2usage( -verbose => 1 ) if( $help ); pod2usage( -verbose => 2 ) if( $manual ); print STDERR "Impossible!\n"; exit(2); =head1 NAME program - a program =head1 SYNOPSIS program ( --help | -- manual ) =head1 DESCRIPTION Prints either short help, or long help. =head1 OPTIONS =over =item B<--help> Print a brief help message and exits. =item B<--manual> Prints the manual page and exits. =back =cut
Subject: Re: [rt.cpan.org #38245] Solved
Date: Thu, 07 Aug 2008 18:18:00 +1000
To: bug-Pod-Parser [...] rt.cpan.org
From: Paul Matthews <plm [...] netspace.net.au>
As the file in question had been back and forward from work to home via a windows machine it had picked up \n\r's. These seems to throw pod2usage( -verbose => 1 ) off balance. Still a bug, but fixed. -- Fools ignore complexity. Pragmatists suffer it. Some can avoid it. Geniuses remove it.
I could not reproduce the problem with my to-become-Pod-Parser-1.36; i.e. I tried your code with perl 5.8.8 on a Solaris box, adding \r before or after the \n - both --help and --man worked OK. Can you attach the version of the file which did not work? -Marek
I just released Pod-Parser-1.36 on CPAN - could you please check whether it still has this problem? If yes, can you send me the input file which shows this issue? Cheers, Marek On Thu Aug 07 04:18:19 2008, plm@netspace.net.au wrote: Show quoted text
> As the file in question had been back and forward from work to home via > a windows machine it had picked up \n\r's. These seems to throw > pod2usage( -verbose => 1 ) off balance. Still a bug, but fixed.
Looks like this is OK now.