Mercurial > pidgin.yaz
view doc/savedstatus-signals.dox @ 29006:588fb0db1cd8
I'm not comfortable with this being an assert. If it fails then Pidgin
crashes. I don't think a fatal check like this should exist in the init
function of a prpl unless it's dangerous for the application to continue
running. I can't imagine why that would be the case here.
People also seem concerned about this struct definition:
struct raw_chunk {
guint8 type;
guint32 length;
gchar data[0];
} __attribute__ ((packed));
I'll probably investigate a little bit
author | Mark Doliner <mark@kingant.net> |
---|---|
date | Mon, 23 Nov 2009 00:19:33 +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