Skip Menu |

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

This queue is for tickets about the MooseX-App CPAN distribution.

Report information
The Basics
Id: 102533
Status: resolved
Priority: 0/
Queue: MooseX-App
People
Owner: Nobody in particular
Requestors: rharkins [...] scenariolearning.com
Cc:
AdminCc:
Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)

History Show all quoted text
  Thu Mar 05 12:23:23 2015 rharkins [...] scenariolearning.com - Ticket created
Subject: Exit code
Date: Thu, 5 Mar 2015 12:22:49 -0500
To: bug-MooseX-App [...] rt.cpan.org
From: Rich Harkins <rharkins [...] scenariolearning.com>
What is the best way to get a proper exit code from the call when usage or command line parsing fails? The current ::Null seems to give very little help in this regard. -- RICH HARKINSSoftware Developer Scenario Learning *o. * 800.434.0154 ScenarioLearning.com <http://scenariolearning.com/> <https://www.facebook.com/scenariolearning> <https://www.linkedin.com/company/scenario-learning> <https://twitter.com/SafeSchoolsNews>
  Sat Mar 21 14:40:35 2015 MAROS [...] cpan.org - Correspondence added
On Thu Mar 05 12:23:23 2015, rharkins@scenariolearning.com wrote: Show quoted text
> What is the best way to get a proper exit code from the call when usage or > command line parsing fails? The current ::Null seems to give very little > help in this regard.
As of MooseX::App 1.32 message classes not support exit codes. You can either check for an exitcode and exit yourself, or let overload handle it and exit for you
  Sat Mar 21 14:40:35 2015 The RT System itself - Status changed from 'new' to 'open'
  Sat Mar 21 14:40:36 2015 MAROS [...] cpan.org - Status changed from 'open' to 'resolved'