Description: ------------ There is no way to have custom error messages for missing arguments, options, etc. For example, I'm defining a sub-command `create' which requires a name argument. Using the documentation, I see I can catch an exception and display its message, resulting in the following: "Error: You must provide at least 1 argument." What I'd really like to display to the user here is: "No queue name specified." After discussing with David, it seems the best way to implement this would be to create different exception classes and provide a method to get the error element. * Console_CommandLine_Exception * Console_CommandLine_OptionException::getErrorElement() * Console_CommandLine_ArgumentException::getErrorElement() * Console_CommandLine_SubCommandException::getErrorElement() * etc... All child exceptions would return the element that caused the error. See the test script for am example. Test script: --------------- try { $result = $parser->parse(); } catch (Console_CommandLine_ArgumentException $exc) { $argument = $exc->getErrorElement(); if ($argument->name == 'queue') { $parser->displayError('No queue name specified.'); } } catch (...) { // etc... }

The following patch has been added/updated: Patch Name: custom-messages-2009-06-19.diff Revision: 1245390825 URL: http://pear.php.net/bugs/patch-display.php?bug=15324&patch=custom-messages-2009-06-19.diff&revision=1245390825&display=1

The attached patch adds support for specifying custom messages. A new interface Console_CommandLine_CustomMessageProvider is added to preserve backwards compatibility with the existing Console_CommandLine_MessageProvider interface. Unit tests for custom messages are added and existing tests are updated to work with new object properties.

you rock Mike ! 1.0.7 released