Mercurial > pidgin.yaz

view pidgin/gtksourceview-marshal.h @ 32635:63e7d226b760

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Re-arrange these doxygen comments. For comments longer than a few words, putting the comment before the variable like this seems cleaner than trying to cram it on the same line as the variable and using lots of crazy indentation. Anyone have a strong opinion either way?
author Mark Doliner <mark@kingant.net>
date Sun, 18 Sep 2011 20:18:33 +0000
parents 674d8bc2b980
children
line wrap: on
line source


#ifndef __gtksourceview_marshal_MARSHAL_H__
#define __gtksourceview_marshal_MARSHAL_H__

#include	<glib-object.h>

G_BEGIN_DECLS

/* VOID:VOID (gtksourceview-marshal.list:1) */
#define gtksourceview_marshal_VOID__VOID	g_cclosure_marshal_VOID__VOID

/* VOID:BOOLEAN (gtksourceview-marshal.list:2) */
#define gtksourceview_marshal_VOID__BOOLEAN	g_cclosure_marshal_VOID__BOOLEAN

/* VOID:BOXED (gtksourceview-marshal.list:3) */
#define gtksourceview_marshal_VOID__BOXED	g_cclosure_marshal_VOID__BOXED

/* VOID:BOXED,BOXED (gtksourceview-marshal.list:4) */
extern void gtksourceview_marshal_VOID__BOXED_BOXED (GClosure     *closure,
                                                     GValue       *return_value,
                                                     guint         n_param_values,
                                                     const GValue *param_values,
                                                     gpointer      invocation_hint,
                                                     gpointer      marshal_data);

/* VOID:STRING (gtksourceview-marshal.list:5) */
#define gtksourceview_marshal_VOID__STRING	g_cclosure_marshal_VOID__STRING

G_END_DECLS

#endif /* __gtksourceview_marshal_MARSHAL_H__ */