Mercurial > pidgin
comparison plugins/notify.c @ 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 | 8d1cf3f847b1 |
children | 71299d63801d |
comparison
equal
deleted
inserted
replaced
12599:e94c33909aa6 | 12600:e856f985a0b9 |
---|---|
822 return TRUE; | 822 return TRUE; |
823 } | 823 } |
824 | 824 |
825 static GaimGtkPluginUiInfo ui_info = | 825 static GaimGtkPluginUiInfo ui_info = |
826 { | 826 { |
827 get_config_frame | 827 get_config_frame, |
828 0 /* page_num (Reserved) */ | |
828 }; | 829 }; |
829 | 830 |
830 static GaimPluginInfo info = | 831 static GaimPluginInfo info = |
831 { | 832 { |
832 GAIM_PLUGIN_MAGIC, | 833 GAIM_PLUGIN_MAGIC, |