>> -                if (error == EPIPE)
>> -                        psignal(p, SIGPIPE);
>> +                if ((error == EPIPE) && !(flags & MSG_NOSIGNAL))
>> +                        psignal(p, SIGPIPE);
> If you do this, you would have version compatibility issues.

Only for new code that actually has a use for the feature.

> Maybe a nice additional feature, but increases the burden on the app
> space to be compatible between versions that do and don't support
> this.

...or to blow off compatability with versions that don't.

Yes.  And?

This is true of *any* new API.  Whether this particular innovation is
worth trying is perhaps arguable.  But I don't think there's really
much question over whether innovation in general is worth doing, and
you can't do a new API without exactly this kind of backward
compatability issue.

In this case, furthermore, the innovation has already happened and has
already made it into application code - that's what started the thread
off.  So doing this wouldn't even be innovating!

/~\ The ASCII				der Mouse
\ / Ribbon Campaign
 X  Against HTML	       mouse@rodents.montreal.qc.ca
/ \ Email!	     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B