Re: Interpreting exit code given to "exit" procedure

Show/hide message thread

Interpreting exit code given to "exit" procedure Lassi Kortela (14 Aug 2019 14:36 UTC)
Re: Interpreting exit code given to "exit" procedure John Cowan (14 Aug 2019 19:49 UTC)
Re: Interpreting exit code given to "exit" procedure Lassi Kortela (14 Aug 2019 20:50 UTC)
Re: Interpreting exit code given to "exit" procedure Lassi Kortela (14 Aug 2019 20:54 UTC)
Re: Interpreting exit code given to "exit" procedure John Cowan (14 Aug 2019 20:57 UTC)
Re: Interpreting exit code given to "exit" procedure Lassi Kortela (14 Aug 2019 21:10 UTC)
(missing)
Fwd: Interpreting exit code given to "exit" procedure John Cowan (14 Aug 2019 21:34 UTC)
Re: Interpreting exit code given to "exit" procedure John Cowan (14 Aug 2019 21:36 UTC)
Re: Interpreting exit code given to "exit" procedure Lassi Kortela (14 Aug 2019 21:45 UTC)
Re: Fwd: Interpreting exit code given to "exit" procedure Lassi Kortela (14 Aug 2019 21:41 UTC)
Re: Fwd: Interpreting exit code given to "exit" procedure John Cowan (14 Aug 2019 22:26 UTC)
Re: Fwd: Interpreting exit code given to "exit" procedure Lassi Kortela (15 Aug 2019 06:43 UTC)

Re: Interpreting exit code given to "exit" procedure Lassi Kortela 14 Aug 2019 21:09 UTC

> Erroring on exact ints outside the range 0-255 works for me when SRFI
> 170 is available.

Great, let's do it.

But unless the programmer is catching that error, it may lead to an exit
with a different exit code :) We should figure out which. Code 1 is not
a good error-exit code, because it's quite often used as boolean false
(e.g. grep uses code 1 to indicate it didn't find any matches.