Re: Writing to closed network port causes guile to exit with error 141, not error message

2024-03-23 Thread Chris Vine
On Fri, 22 Mar 2024 19:00:43 -0400 Ryan Raymond wrote: > Thank you, Thomas. > I do wonder if this is good behavior to have in Guile. I feel like we > should replace that signal with an error. It's not good for programs to > exit without an explanation. > > However, thank you for your help. > Ryan

Re: Writing to closed network port causes guile to exit with error 141, not error message

2024-03-22 Thread Ryan Raymond
Thank you, Thomas. I do wonder if this is good behavior to have in Guile. I feel like we should replace that signal with an error. It's not good for programs to exit without an explanation. However, thank you for your help. Ryan On Fri, Mar 22, 2024 at 12:05 PM Tomas Volf <~@wolfsden.cz> wrote:

Re: Writing to closed network port causes guile to exit with error 141, not error message

2024-03-22 Thread Tomas Volf
Hi, On 2024-03-22 10:22:03 -0400, Ryan Raymond wrote: > Hello, all > I have a problem with my web-server. > If the network connection to the server is closed (by killing the client) > and one attempts to write data to that port in GUILE, the interpreter will > exit without an error message. echo "

Writing to closed network port causes guile to exit with error 141, not error message

2024-03-22 Thread Ryan Raymond
Hello, all I have a problem with my web-server. If the network connection to the server is closed (by killing the client) and one attempts to write data to that port in GUILE, the interpreter will exit without an error message. echo "$?" says GUILE exited with error code 141 but google doesn't give