view plugins/mono/api/Debug.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 <[e-mail]>

using System;
using System.Runtime.CompilerServices;

namespace Gaim
{
	public class Debug
	{
		public static int ALL = 0;
		public static int MISC = 1;
		public static int INFO = 2;
		public static int WARNING = 3;
		public static int ERROR = 4;
		public static int FATAL = 5;
		
		[MethodImplAttribute(MethodImplOptions.InternalCall)]
		extern private static void _debug(int type, string cat, string str);
		
		public static void debug(int type, string cat, string format)
		{
			_debug(type, cat, format);
		}
		
		public static void debug(int type, string cat, string format, params object[] args)
		{
			_debug(type, cat, String.Format(format, args));
		}
	}
}