|Comments on Wednesday 4 December 2002:|
|And a bit more GNUish complaint, though this is more of a Unix thing really - whose stupid idea was it to produce the following combination?|
1. By default, a failing send or a failing recv - a failure generally brought about by the other machine involved in the connection disconnecting - causes a SIGPIPE signal to be sent.
2. The default action upon receiving a SIGPIPE signal - an event which can occur at any point in your program - is for the process to exit suddenly without any explanation whatsoever.Thanks go to the people who did so, for wasting a shitload of my time. Bastards. [09:51]
|And grarh again.|
|Aha. Ravenblack has lured somebody else into a dark alley and devoured their comment?|
I think you should probably blame BSD people for this ultimately.
|Ah, but ultimately, the BSD people are blamed for everything. No need to go about wasting effort blaming them now when they will inevitably be blamed for some equally irksome occurance later.|
Then again, there's always the satisfaction of being able to say 'Haha<\/A>/, I did it first!'