im.pidgin.pidgin: 70b395d226d80e7490383a8d0f7e77438cace2ab

[rlaager at pidgin.im]

-----------------------------------------------------------------
Revision: 70b395d226d80e7490383a8d0f7e77438cace2ab
Ancestor: 1666e4ac675420b25c9763e9e38caac93d16c5b0
Author: rlaager at pidgin.im
Date: 2008-01-05T17:14:32
Branch: im.pidgin.pidgin

Modified files:
        libpurple/core.h

ChangeLog: 

Clarify a comment that was confusing me. Thanks resiak!

-------------- next part --------------
============================================================
--- libpurple/core.h	583177e6431d025d95adf80bf968053a41a199ff
+++ libpurple/core.h	b1496d8cc24af7606f6de8793e2f2d560fcb40b7
@@ -67,13 +67,14 @@ void purple_core_quit(void);
  * 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);