Skip Menu |

This queue is for tickets about the Getopt-Euclid CPAN distribution.

Report information
The Basics
Id: 28474
Status: resolved
Priority: 0/
Queue: Getopt-Euclid

People
Owner: Nobody in particular
Requestors: toddr [...] cpanel.net
Cc:
AdminCc:

Bug Information
Severity: Normal
Broken in: v0.1.0
Fixed in: v0.2.2



We discovered today that if "=head1 NAME" has an empty body or if it's only $0, we get the following error and some of the euclid features do not work as expected. for instance we had a "parameter.type = / \d\d\d\d/" and it did not look for 4 digit numbers as expected. Tod fix this, NAME must have "$0 - something here" below it to function. ---- Example =head1 USAGE Euclid auto-generates this. Run program with --help for usage. =head1 VERSION version 1.0 =head1 NAME $0 =head1 REQUIRED ARGUMENTS =over ---- End Example
Subject: Correction
From: todd.e.rinaldo [...] jpmorgan.com
NOTE: The example is how to create a bug, not how it should be
Subject: Additional evidence of break
From: todd.e.rinaldo [...] jpmorgan.com
if NAME is setup wrong, you will also get an obscure message not pointing to the problem that says: POD ERRORS Hey! The above document had some coding errors, which are explained below: Around line 20: '=item' outside of any '=over'
On Wed Jul 25 11:38:41 2007, todd_rinaldo wrote: Show quoted text
> if NAME is setup wrong, you will also get an obscure message not > pointing to the problem that says: > > POD ERRORS > Hey! The above document had some coding errors, which are explained > below: > > Around line 20: > '=item' outside of any '=over'
This is the only error I was able to replicate. I will fix this when I get to reworking how Getopt::Euclid reads the pod (currently it is done all through regular expressions, and I hope to switch it over to Pod::Parser)
#!/usr/bin/env perl use strict; use warnings; use Getopt::Euclid; =head1 NAME =head1 OPTIONS =over =item -foo =back =cut
I wasn't able to get the same error you found, but I fixed the way the name was being parsed.