Mercurial > pidgin.yaz
view libpurple/dbus-maybe.h @ 32363:3322201b446f
I went through all our calls to purple_notify_user_info_add_pair() and
checked whether they should be purple_notify_user_info_add_pair_plaintext(),
instead. If it wasn't immediately obvious one way or the other then I
left a comment to investigate. I suspect there are still a lot of places
where we should use the _plaintext function to escape the value.
author | Mark Doliner <mark@kingant.net> |
---|---|
date | Mon, 22 Aug 2011 01:53:37 +0000 |
parents | 1568dc7a14f8 |
children |
line wrap: on
line source
/* This file contains macros that wrap calls to the purple dbus module. These macros call the appropriate functions if the build includes dbus support and do nothing otherwise. See "dbus-server.h" for documentation. */ #ifndef _PURPLE_DBUS_MAYBE_H_ #define _PURPLE_DBUS_MAYBE_H_ #ifdef HAVE_DBUS #ifndef DBUS_API_SUBJECT_TO_CHANGE #define DBUS_API_SUBJECT_TO_CHANGE #endif #include "dbus-server.h" /* this provides a type check */ #define PURPLE_DBUS_REGISTER_POINTER(ptr, type) { \ type *typed_ptr = ptr; \ purple_dbus_register_pointer(typed_ptr, PURPLE_DBUS_TYPE(type)); \ } #define PURPLE_DBUS_UNREGISTER_POINTER(ptr) purple_dbus_unregister_pointer(ptr) #else /* !HAVE_DBUS */ #define PURPLE_DBUS_REGISTER_POINTER(ptr, type) { \ if (ptr) {} \ } #define PURPLE_DBUS_UNREGISTER_POINTER(ptr) #define DBUS_EXPORT #endif /* HAVE_DBUS */ #endif