[Larceny-users] no exit status?

[Jon Wells]

G'day,
I don't seem to be able to get larceny to return a status to the OS...

Off the shelf, linux binary...

Larceny v0.98 "General Ripper" (Mar 7 2015 01:06:26, precise:Linux:unified)
larceny.heap, built on Sat Mar 7 01:06:50 EST 2015

(import (primitives exit))
(exit 42)

0

Doesn't seem to matter which byte I put the status in...

(exit (* 256 256 256 42))

0

Or whether or not it's in R7 mode.

jon.

[William D Clinger]

Post by Jon Wells
I don't seem to be able to get larceny to return a status to the OS...

I think that's a bug in Larceny v0.98 that's been fixed in the current
development system:

% larceny
Larceny v0.98 "General Ripper" (Mar 7 2015 01:24:18, precise:Posix:unified)
larceny.heap, built on Sat Mar 7 01:25:38 EST 2015

Post by Jon Wells
(exit 42)

% echo $?
0
% ./larceny
Larceny v0.98+ "General Ripper" (Feb 28 2016 20:08:51, precise:Posix:unified)
larceny.heap, built on Sun Feb 28 20:10:06 EST 2016

Post by Jon Wells
(exit 42)

% echo $?
42

Please see whether the problem is present in the nightly build:

http://larceny.ccs.neu.edu/nightly/

Tests of the exit status have been added to Larceny's R7RS tests,
and the nightly builds have been passing those tests, but there's
always the possibility of a bum test or some system-specific problem.

Will

[Jon Wells]

That works, I'll switch to it, thanks Will.

jon.

Post by William D Clinger

Post by Jon Wells
I don't seem to be able to get larceny to return a status to the OS...

I think that's a bug in Larceny v0.98 that's been fixed in the current
% larceny
Larceny v0.98 "General Ripper" (Mar 7 2015 01:24:18, precise:Posix:unified)
larceny.heap, built on Sat Mar 7 01:25:38 EST 2015

Post by Jon Wells
(exit 42)

% echo $?
0
% ./larceny
Larceny v0.98+ "General Ripper" (Feb 28 2016 20:08:51, precise:Posix:unified)
larceny.heap, built on Sun Feb 28 20:10:06 EST 2016

Post by Jon Wells
(exit 42)

% echo $?
42
http://larceny.ccs.neu.edu/nightly/
Tests of the exit status have been added to Larceny's R7RS tests,
and the nightly builds have been passing those tests, but there's
always the possibility of a bum test or some system-specific problem.
Will