Skip Menu |

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

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

People
Owner: Nobody in particular
Requestors: djerius [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Important
Broken in: v0.2.0
Fixed in: (no value)



Subject: Prevent command line processing during compilation only runs
My development framework automatically runs perl -wc on code, which usually produces succinct output upon success. However, since I don't provide actual arguments to the code, running this on a program which has required options results in Getopt::Euclid generating a usage statement. It would be useful if Getopt::Euclid could recognize that it's in compile only mode and not perform command line processing. Or, if that's not possible, have it monitor an environment variable (or something!) to make it not perform the processing. Thanks, Diab
Subject: compilation only runs don't report errors.
Whoops. I'm bumping this up to a bug. If there's a required option and you run perl -wc on the code, it interferes with the compilation and doesn't report compilation errors. For example, running perl -wc on the following code: #!/usr/bin/perl use strict; use warnings; use Getopt::Euclid; $foo = 1; __END__ =head1 REQUIRED ARGUMENTS =over =item <prefix> The string used to prefix the output file name(s). =back results in: % perl -wc ~/tmp/goe Missing required argument: <prefix> (Try: goe --help) But it really should result in a compiler error. Commenting out the "use Getopt::Euclid" line results in: % perl -wc ~/tmp/goe Global symbol "$foo" requires explicit package name at /home/dj/tmp/goe line 8.
Should be fixed in 0.2.4. Thanks for reporting!