annotate plugins/mono/api/Event.cs @ 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 |
a3302d271199 |
| children |
|
| rev |
line source |
|
11660
|
1 using System;
|
|
|
2
|
|
|
3 namespace Gaim
|
|
|
4 {
|
|
|
5 public class Event
|
|
|
6 {
|
|
|
7 private IntPtr handle;
|
|
|
8 private string signal;
|
|
|
9
|
|
|
10 public Event(IntPtr h, string s)
|
|
|
11 {
|
|
|
12 handle = h;
|
|
|
13 signal = s;
|
|
|
14 }
|
|
|
15
|
|
|
16 public void connect(object plugin, Signal.Handler handler)
|
|
|
17 {
|
|
|
18 Signal.connect(handle, plugin, signal, handler);
|
|
|
19 }
|
|
|
20 }
|
|
|
21 }
|