view src/dbus-define-api.h @ 13905:4e44ecb866bd

[gaim-migrate @ 16394] msn_session_sync_users() iterates over the buddy list, following the ->next pointers of the groups, contacts, and buddies. msn_show_sync_issue(), if called, removed the buddy for which it was called, in preparation for the buddy either being added to the server list or confirmed-to-be-removed. This could lead to the buddy pointer being released and ->next therefore being junk. The buddy is now not removed until the user responds to the action dialog presented via msn_show_sync_issue(). I'm unclear why gtkgaim got away with this exercise in memory stomping but Adium/libgaim crashed every time, but it's safer in any case. I also changed some foo->bar to gaim_foo_get_bar(). committer: Tailor Script <[e-mail]>

#error "This is file is not a valid C code"

/* This file contains some of the macros from other header files as
   function declarations.  This does not make sense in C, but it
   provides type information for the dbus-analyze-functions.py
   program, which makes these macros callable by DBUS.  */

/* blist.h */
gboolean GAIM_BLIST_NODE_IS_CHAT(GaimBlistNode *node);
gboolean GAIM_BLIST_NODE_IS_BUDDY(GaimBlistNode *node);   
gboolean GAIM_BLIST_NODE_IS_CONTACT(GaimBlistNode *node);
gboolean GAIM_BLIST_NODE_IS_GROUP(GaimBlistNode *node);
gboolean GAIM_BUDDY_IS_ONLINE(GaimBuddy *buddy); 
gboolean GAIM_BLIST_NODE_HAS_FLAG(GaimBlistNode *node, int flags);
gboolean GAIM_BLIST_NODE_SHOULD_SAVE(GaimBlistNode *node);

/* connection.h */
gboolean GAIM_CONNECTION_IS_CONNECTED(GaimConnection *connection);
gboolean GAIM_CONNECTION_IS_VALID(GaimConnection *connection);

/* conversation.h */
GaimConvIm *GAIM_CONV_IM(const GaimConversation *conversation);
GaimConvIm *GAIM_CONV_CHAT(const GaimConversation *conversation);