Mercurial > pidgin
changeset 22010:7e5ecf03b69d
Clarify a comment that was confusing me. Thanks resiak!
| author | Richard Laager <rlaager@wiktel.com> |
|---|---|
| date | Sat, 05 Jan 2008 17:14:32 +0000 |
| parents | 1494e0a0f2b9 |
| children | 76e0463db3aa |
| files | libpurple/core.h |
| diffstat | 1 files changed, 6 insertions(+), 5 deletions(-) [+] |
line wrap: on
line diff
--- a/libpurple/core.h Sat Jan 05 16:32:40 2008 +0000 +++ b/libpurple/core.h Sat Jan 05 17:14:32 2008 +0000 @@ -67,13 +67,14 @@ * Calls purple_core_quit(). This can be used as the function * passed to purple_timeout_add() when you want to shutdown Purple * in a specified amount of time. When shutting down Purple - * from a plugin, you must use this with a timeout value of 0: + * from a plugin, you must use this instead of purple_core_quit(); + * for an immediate exit, use a timeout value of 0: * purple_timeout_add(0, purple_core_quitcb, NULL); * This is ensures that code from your plugin is not being - * executed when purple_core_quit() is called. Otherwise you - * would get a core dump after purple_core_quit() executes and - * control returns to your plugin because purple_core_quit() frees - * all plugins. + * executed when purple_core_quit() is called. If the plugin + * called purple_core_quit() directly, you would get a core dump + * after purple_core_quit() executes and control returns to your + * plugin because purple_core_quit() frees all plugins. */ gboolean purple_core_quit_cb(gpointer unused);