annotate doc/core-signals.dox @ 12600:e856f985a0b9
[gaim-migrate @ 14934]
Enable the extra warnings regardless of --enable-debug.
Enable FORTIFY_SOURCE regardless of --enable-debug, adding a --disable-fortify flag to configure.
Enable (well, stop disabling) the missing initializer warnings.
This leads to warnings with: GValue v = {0,}; that must be worked around.
Basically, instead of:
GValue v = {0,};
...
g_value_init(&v, G_TYPE_FOO); /* or other use of the GValue */
We'd need to do:
GValue v;
...
v.g_type = 0;
g_value_init(&v, G_TYPE_FOO); /* or other use of the GValue */
Fix several cases of missing initializers. I don't think any of these are bugs, but having this warning seems like a good idea. It might prevent us from making a mistake in the future.
While I was fixing missing initializers, I optimized substitute_simple_word in plugins/spellchk.c, in the same way as I did substitute_word before. Yes, I'm bad for committing these together.
Added a --enable-fatal-asserts flag to configure. As the name implies, this makes g_return_... guards fatal. This is a useful flag to run on a debug copy of Gaim. It will make it very clear if your changes have triggered one of these guards. It's also useful in detecting g_return_... abuse, which helps prevent crashes if Gaim is compiled with G_DISABLE_ASSERT defined.
committer: Tailor Script <tailor@pidgin.im>
| author |
Richard Laager <rlaager@wiktel.com> |
| date |
Wed, 21 Dec 2005 18:36:19 +0000 |
| parents |
1ec93dd2f359 |
| children |
1414e0e01dc5 |
| rev |
line source |
|
12053
|
1 /** @page core-signals Core Signals
|
|
|
2
|
|
|
3 @signals
|
|
|
4 @signal quitting
|
|
|
5 @endsignals
|
|
|
6
|
|
|
7 <hr>
|
|
|
8
|
|
|
9 @signaldef quitting
|
|
|
10 @signalproto
|
|
|
11 void (*quitting)();
|
|
|
12 @endsignalproto
|
|
|
13 @signaldesc
|
|
|
14 Emitted when gaim is quitting.
|
|
|
15 @endsignaldef
|
|
|
16
|
|
|
17 */
|
|
|
18 // vim: syntax=c tw=75 et
|
