On Fri 27 Aug 2010 07:01, Jon Herron <[email protected]> writes: > Hi Andy - > > Thanks for the reply. I think SIGPIPE is indeed the right thing to do. I > ended > up adding a sighandler to my application and it solved the problem. I suppose > it > would be nice for Guile to at least display the error on exit - as in the gdb > REPL example of yours, if not throw an exception so the user's application > can > catch. It seems to me the sighandler is more of the C way, where catch/throw > is > closer to the Scheme way - not sure if that is general consensus or not.
I filed this bug. https://savannah.gnu.org/bugs/index.php?30890 I think you're right that we should handle signals, but we need to do so in a way that is not going to interfere adversely with embedded uses of Guile. And then there are threads. Bleagh ;) Andy -- http://wingolog.org/
