comparison libpurple/prefs.c @ 16342:b1c1b2319616

When initializing, the debug system is initialized before the prefs system, but debug calls will end up calling prefs functions, so we need to deal with that situation cleanly. I noticed this when using the debug functions in the core migration code.

16326:08557e94840c

	g_return_val_if_fail(name != NULL && name[0] == '/', NULL);

	if (name[1] == '\0')
		return &prefs;
	else
		return g_hash_table_lookup(prefs_hash, name);
}


/*********************************************************************
 * Writing to disk                                                   *

16342:b1c1b2319616

	g_return_val_if_fail(name != NULL && name[0] == '/', NULL);

	if (name[1] == '\0')
		return &prefs;
	else
	{
		/* When we're initializing, the debug system is
		 * initialized before the prefs system, but debug
		 * calls will end up calling prefs functions, so we
		 * need to deal cleanly here. */
		if (prefs_hash)
			return g_hash_table_lookup(prefs_hash, name);
		else
			return NULL;
	}
}


/*********************************************************************
 * Writing to disk                                                   *