Mercurial > pidgin.yaz
view doc/gtkaccount-signals.dox @ 12435:8f98014a4e7d
[gaim-migrate @ 14742]
1. Protecting the --enable-debug warning tests with an "if gcc" check.
2. Adding a number of warning flags to --enable-debug. All cases of the added warnings have been fixed, except:
a. The pointer-arith warnings. I think someone smarter than me should decide whether we need to fix those (and how) or if that should be disabled. That said, I think all the errors left (after you consider the exception listed as "b" below) are in libzephyr.
b. Those in src/protocols/sametime/meanwhile at siege's request. Don't worry about these for now.
3. Noting a few warnings we could enable, and the cases we'd have to deal with. Thoughts on these warnings?
4. I added support for FORTIFY_SOURCE. If your compiler has support for this feature, --enable-debug will set _FORTIFY_SOURCE=2. I'm doing this in --enable-debug for the warnings you get. I wouldn't mind having it on by default for the runtime protections as well. Thoughts?
committer: Tailor Script <tailor@pidgin.im>
author | Richard Laager <rlaager@wiktel.com> |
---|---|
date | Fri, 09 Dec 2005 05:32:59 +0000 |
parents | 5bc3d67ceb24 |
children | 8cf53d7a0887 |
line wrap: on
line source
/** @page gtkaccount-signals GtkAccount Signals @signals @signal account-modified @endsignals <hr> @signaldef account-modified @signalproto void (*account-modified)(GaimAccount *account); @endsignalproto @signaldesc Emitted when the settings for an account have been changed and saved. @param account The account that has been modified. @endsignaldef */ // vim: syntax=c tw=75 et