Mercurial > pidgin
comparison plugins/ChangeLog @ 394:f73dc7d32ede
[gaim-migrate @ 404]
whoops
committer: Tailor Script <tailor@pidgin.im>
author | Eric Warmenhoven <eric@warmenhoven.org> |
---|---|
date | Mon, 12 Jun 2000 13:18:11 +0000 |
parents | df5127560034 |
children | 59d97cd251ff |
comparison
equal
deleted
inserted
replaced
393:bbff7d508593 | 394:f73dc7d32ede |
---|---|
10 | 10 |
11 The big thing to note is that gaim_plugin_init no longer returns void, | 11 The big thing to note is that gaim_plugin_init no longer returns void, |
12 but int. If it returns 1, gaim interprets this as there being no | 12 but int. If it returns 1, gaim interprets this as there being no |
13 error, and continues with loading as normal. (This should be backwards- | 13 error, and continues with loading as normal. (This should be backwards- |
14 compatible: returning 1 is the equivalent of returning void.) If it | 14 compatible: returning 1 is the equivalent of returning void.) If it |
15 returns a non-zero number, there was an error loading detected by the | 15 returns a number other than 1, there was an error loading detected by |
16 plugin. At that point, gaim will try to clean things up by removing any | 16 the plugin. At that point, gaim will try to clean things up by removing |
17 callbacks that have been added by the plugin. It will then try to call | 17 any callbacks that have been added by the plugin. It will then try to |
18 the plugin's gaim_plugin_error function, if there is one. The function | 18 call the plugin's gaim_plugin_error function, if there is one. The |
19 should take an int (the int returned by gaim_plugin_init) and return a | 19 function should take an int (the int returned by gaim_plugin_init) and |
20 char*. If the char* is not NULL, it is displayed by gaim as an error | 20 return a char*. If the char* is not NULL, it is displayed by gaim as an |
21 message. The plugin is then unloaded and closed and life goes back to | 21 error message. The plugin is then unloaded and closed and life goes |
22 normal. If any of that was confusing, it was confusing to me, too. I | 22 back to normal. If any of that was confusing, it was confusing to me, |
23 added a plugin, error.c, which should help clear things up. | 23 too. I added a plugin, error.c, which should help clear things up. |
24 | 24 |
25 There is a new event, event_quit, which signifies that gaim has exited | 25 There is a new event, event_quit, which signifies that gaim has exited |
26 correctly (i.e. didn't segfault). Also, after this event is called, all | 26 correctly (i.e. didn't segfault). Also, after this event is called, all |
27 plugins are removed, and their gaim_plugin_init function is called. | 27 plugins are removed, and their gaim_plugin_init function is called. |
28 This behavior is different from previous versions; however, it is the | 28 This behavior is different from previous versions; however, it is the |