view src/dbus-define-api.h @ 13771:463259ea22ff

[gaim-migrate @ 16183] Apparently if you just use --with-python the autotools decide you must mean you want to use yes(1) as your python interpreter, this results in an infinitely growing output file the first time the dbus stuff tries to generate a header. That's bad. This should make it a bit clearer. 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);