On Sunday 08 April 2007 06:37, James Keenan via RT wrote: > On Sun Apr 08 00:07:13 2007, [EMAIL PROTECTED] wrote:
> > When Parrot processes its command-line arguments, it detects valid and > > invalid flags and reports invalid flags, then exits with an exit code of > > 1. > > I could find no tests for this feature. They would be lovely to have. > > A week ago I submitted a patch which extracted the CL argument processing > functionality from Configure.pl and placed it in > lib/Parrot/Configure/Options.pm. The purpose of the patch was specifically > to improve the testability of the functionality in Configure.pl. The patch > also included a test file, t/configure/01-options.t, which, among other > things, included a test for an invalid option. I mean the command-line arguments to the parrot executable, not Configure.pl. -- c
