Bug #58836 for Getopt-Long: GetOptionsFromArray dies without error message

Fri Jun 25 12:13:38 2010 bitcard [...] froods.org - Ticket created

Subject:

GetOptionsFromArray dies without error message

I haven't been able to trace the source of the problem so far, so I'm crossposting here in case you guys have any insight... I'm running into a problem interacting with MooseX::ConfigFile, MooseX::Runnable and MooseX::Getopt where it calls into Getopt::Long. See: http://www.nntp.perl.org/group/perl.moose/2010/06/msg1765.html GetOptionsFromArray() is dying in the eval{} block around line 582 -- somehow, the $configfile scalarref is becoming undef even though it is being passed in.

Fri Jun 25 13:54:55 2010 bitcard [...] froods.org - Correspondence added

From:

bitcard [...] froods.org

On Fri Jun 25 12:13:38 2010, bitcard@froods.org wrote: Show quoted text

> I haven't been able to trace the source of the problem so far, so I'm > crossposting here in case you guys have any insight... I'm running into > a problem interacting with MooseX::ConfigFile, MooseX::Runnable and > MooseX::Getopt where it calls into Getopt::Long. > > See: http://www.nntp.perl.org/group/perl.moose/2010/06/msg1765.html > > GetOptionsFromArray() is dying in the eval{} block around line 582 -- > somehow, the $configfile scalarref is becoming undef even though it is > being passed in.

More details after further investigation... the death* is inside the pod2usage call (in &HelpMessage), caused by a misconfiguration of the auto_help option in MooseX::Getopt (which I will address through bug reports/patches in that distribution). *and actually the death is an exit (on the last line of pod2usage), so I think this ticket can be closed, as there is no error in Getopt::Long itself.

Tue Oct 12 17:08:03 2010 RUZ_ADMIN - Requestor ETHER added

Tue Oct 12 17:08:03 2010 RUZ_ADMIN - Requestor bitcard@froods.org deleted

Tue Aug 18 08:38:44 2020 jv [...] cpan.org - Status changed from 'new' to 'rejected'