Mercurial > pidgin.yaz
view doc/gtkaccount-signals.dox @ 27390:fc5508709e74
Use glib's SHA1, SHA256, and MD5 implementations when available (glib 2.16)
These SHA1 and SHA256 implementations do not expose any options, which
the built-in ones do (for getting/setting sizeHi, sizeLo, and lenW).
Nothing in Pidgin uses those (and I can't think of a decent use case),
so I think this is OK. Feel free to disagree.
As I mentioned on the mailing list, glib's SHA1 implementation was just
under 3x as fast on my system.
author | Paul Aurich <paul@darkrain42.org> |
---|---|
date | Sat, 04 Jul 2009 23:13:23 +0000 |
parents | e0613cf8c493 |
children |
line wrap: on
line source
/** @page gtkaccount-signals GtkAccount Signals @signals @signal account-modified @endsignals @see gtkaccount.h <hr> @signaldef account-modified @signalproto void (*account-modified)(PurpleAccount *account); @endsignalproto @signaldesc Emitted when the settings for an account have been changed and saved. @param account The account that has been modified. @endsignaldef */ // vim: syntax=c.doxygen tw=75 et