Mercurial > pidgin.yaz
view doc/savedstatus-signals.dox @ 32405:d3d41ba0c3b8
In our forked DNS resolver processes, don't bail out if we get a retryable
error while reading from our parent socket. I think EAGAIN and EWOULDBLOCK
never happen because this is a non-blocking socket AND because we're using
select (seems like we'd be fine using one or the other, and it's not necessary
to use both?). I believe this is correct behavior and we should be doing
this same thing everywhere we read from sockets. I think we probably don't
check for EINTR in many places where we should.
author | Mark Doliner <mark@kingant.net> |
---|---|
date | Wed, 24 Aug 2011 17:54:39 +0000 |
parents | e0613cf8c493 |
children |
line wrap: on
line source
/** @page savedstatus-signals Saved Status Signals @signals @signal savedstatus-changed @endsignals @see savedstatus.h <hr> @signaldef savedstatus-changed @signalproto void (*savedstatus_changed)(PurpleSavedStatus *new, PurpleSavedStatus *old); @endsignalproto @signaldesc Emitted when a new saved status is activated. @endsignaldef */ // vim: syntax=c.doxygen tw=75 et