Mercurial > pidgin
view libpurple/plugins/perl/common/Debug.xs @ 27994:2ee64cfbbe2e
Check in a change that does dumb client-side blocking of people
on your block list, for when the protocol doesn't do it for us.
I think this is the behavior user's expect, and most of us seemed
to be in favor of this when we talked about it on the devel list
recently.
This is really just to hold us over until Sulabh's privay changes
are ready.
| author | Mark Doliner <mark@kingant.net> |
|---|---|
| date | Tue, 18 Aug 2009 22:31:39 +0000 |
| parents | 39c7bb133a9f |
| children |
line wrap: on
line source
#include "module.h" MODULE = Purple::Debug PACKAGE = Purple::Debug PREFIX = purple_debug_ PROTOTYPES: ENABLE BOOT: { HV *stash = gv_stashpv("Purple::Debug", 1); static const constiv *civ, const_iv[] = { #define const_iv(name) {#name, (IV)PURPLE_DEBUG_##name} const_iv(ALL), const_iv(MISC), const_iv(INFO), const_iv(WARNING), const_iv(ERROR), const_iv(FATAL), }; for (civ = const_iv + sizeof(const_iv) / sizeof(const_iv[0]); civ-- > const_iv; ) newCONSTSUB(stash, (char *)civ->name, newSViv(civ->iv)); } void purple_debug(level, category, string) Purple::DebugLevel level const char *category const char *string CODE: purple_debug(level, category, "%s", string); void purple_debug_misc(category, string) const char *category const char *string CODE: purple_debug_misc(category, "%s", string); void purple_debug_info(category, string) const char *category const char *string CODE: purple_debug_info(category, "%s", string); void purple_debug_warning(category, string) const char *category const char *string CODE: purple_debug_warning(category, "%s", string); void purple_debug_error(category, string) const char *category const char *string CODE: purple_debug_error(category, "%s", string); void purple_debug_fatal(category, string) const char *category const char *string CODE: purple_debug_fatal(category, "%s", string); void purple_debug_set_enabled(enabled) gboolean enabled gboolean purple_debug_is_enabled()
