Mercurial > pidgin.yaz
view doc/cmd-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 | 1ca49b349037 |
children |
line wrap: on
line source
/** @page cmd-signals Command Signals @signals @signal cmd-added @signal cmd-removed @endsignals @see cmds.h @signaldef cmd-added @signalproto void (*cmd_added)(const char *command, PurpleCmdPriority priority, PurpleCmdFlag flag); @endsignalproto @signaldesc Emitted when a new command is added. @param command The new command. @param priority The priority of the new command. @param flag The command flags. @endsignaldef @signaldef cmd-removed @signalproto void (*cmd_removed)(const char *command); @endsignalproto @signaldesc Emitted when a command is removed. @param command The removed command. @endsignaldef */