Re: I know that signal handling isn't working well on win32, but how bad is it?

What would happen if the other end of the pipe got broken on win32 ports?

I imagine it would return error EPIPE just like on unix if you were ignoring SIGPIPE. Didn't you try?

But if the $SIG{PIPE} is not working on win32, should I use eval on every piped writing?

Are you using IO functions that throw exceptions on error, then yes, but you have had to do that anyway.

Man, win32 sucks...:(

The only difference is whether the error is fatal or not by default. Having Windows choose to be not fatal by default is hardly a sucky decision.

Comment on Re: I know that signal handling isn't working well on win32, but how bad is it?

Replies are listed 'Best First'.
Re^2: I know that signal handling isn't working well on win32, but how bad is it? by AGhoulDoingPerl (Sexton) on Mar 01, 2011 at 19:37 UTC
... is hardly a sucky decision. Oh,well.. their decision would be fine, but win32 sucks as a whole, anyway :) Thanks for the reply.	[reply]
Re^3: I know that signal handling isn't working well on win32, but how bad is it? by ikegami (Patriarch) on Mar 01, 2011 at 20:22 UTC
Could you give an example? I have the impression that you're not talking about Win32, but about Windows or Microsoft.	[reply]