Mercurial > pidgin
view plugins/perl/common/Stringref.xs @ 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 | 6fd82071a7b8 |
| children | 96f9b4798012 |
line wrap: on
line source
#include "module.h" MODULE = Gaim::Stringref PACKAGE = Gaim::Stringref PREFIX = gaim_stringref_ PROTOTYPES: ENABLE int gaim_stringref_cmp(s1, s2) Gaim::Stringref s1 Gaim::Stringref s2 size_t gaim_stringref_len(stringref) Gaim::Stringref stringref Gaim::Stringref gaim_stringref_new(class, value) const char *value C_ARGS: value Gaim::Stringref gaim_stringref_new_noref(class, value) const char *value C_ARGS: value Gaim::Stringref gaim_stringref_ref(stringref) Gaim::Stringref stringref void gaim_stringref_unref(stringref) Gaim::Stringref stringref const char * gaim_stringref_value(stringref) Gaim::Stringref stringref
