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

> That said, I think EINVAL is the best errno-error to raise when exit and
> emergency-exit are called with out-of-range or unknown arguments.

Alas, it is.

It still seems slightly distasteful to me in principle to fabricate
errno values, though I can't think of any concrete harm in this case.

> Remember that #t (exit code 0) and #f (some exit code) must be supported
> as well.

Right, we should probably pick a particular exit code for #f.