view plugins/mono/api/Debug.cs @ 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 <[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));
		}
	}
}