On 5/9/19 5:45 AM, Lassi Kortela wrote:
> The interface should also translate well to JVM and CLR so it would be good to look at Kawa and IronScheme too. Luckily JVM and CLR both allow calls to native code in case there's something really tricky.

I'm not convinced that direct Scheme access to low-level integer file descriptors and fork are
useful to standardize.

It is better to standardize higher-level APIs. For example Kawa has a flexible high-level process API:
https://www.gnu.org/software/kawa/Processes.html

Doing doing a 'fork' on the JVM using native code seems like a bad idea.  Better to use ProcessBuilder,
which is quite flexible:
https://docs.oracle.com/en/java/javase/12/docs/api/java.base/java/lang/ProcessBuilder.html

I build a single portable "universal" binary release for Kawa. Adding native code would complicate that.
--
	--Per Bothner
xxxxxx@bothner.com   http://per.bothner.com/