Re: [Chicken-hackers] [PATCH] make csi close stdin/stderr/stdout when exiting.

[Christian Kellermann]

* felix winkelmann <address@hidden> [120424 12:31]:

> Is this necessary? What if there is still output from lower levels
> of the runtime system? (say by starting csi with "-:d")?

You loose this output indeed, for example in the best case you won't see:

#;1> ,q
[debug] forcing finalizers...
[debug] application terminated normally
$

So maybe this is not the best way to deal with that. But what other
options are there? Can I explicitly call a finalizer?  Do we have a
way to insert an atexit handler that does not smash either the user's
or can restore the original chain (if at last my own handler
implements a chain, by calling the previous one) when the port is
explicitly closed by the user?

Having cleanup action upon a close seemed a reasonable thing to do.

Maybe it is not.

Kind regards,

Christian

--
9 out of 10 voices in my head say, that I am crazy,
one is humming.