On Fri, Jun 13, 2008 at 8:19 AM, James Keenan via RT
<[EMAIL PROTECTED]> wrote:
> I notice that the *actual* exit code I'm getting is 256. Has that
> changed since the OP or is there some bit-shifting going on here?
>
> I also notice that the same exit code is generated regardless of whether
> the
> I notice that the *actual* exit code I'm getting is 256. Has that
> changed since the OP or is there some bit-shifting going on here?
>
If you are testing the return from a system call, "To get the actual exit
value, divide by 256. (The lower eight bits are set if the process died
from a signal
On Thursday 12 June 2008 18:39:04 James Keenan via RT wrote:
> The attached is very crude -- but is it at all what you were looking for?
It's a good start. See parrot -h for a list of known options. I'm sure you
could make a nice little data-driven test with what you have here now.
-- c
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 t
