After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 477532 - function variables
function variables
Status: RESOLVED FIXED
Product: gtk-doc
Classification: Platform
Component: general
unspecified
Other Linux
: Normal normal
: 1.9
Assigned To: gtk-doc maintainers
gtk-doc maintainers
Depends on:
Blocks:
 
 
Reported: 2007-09-16 16:57 UTC by Matthias Clasen
Modified: 2007-09-22 19:55 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Matthias Clasen 2007-09-16 16:57:37 UTC 
GLib has a 

GLIB_VAR guint64   (*g_thread_gettime) (void);

declaration in a public header, which really confuses gtk-doc:

###Can't parse args for function guint64: *g_thread_gettime) (void
Comment 1 Stefan Sauer (gstreamer, gtkdoc dev) 2007-09-17 21:28:48 UTC 
If I understood right we could just replace this by 'extern'?
Comment 2 Stefan Sauer (gstreamer, gtkdoc dev) 2007-09-17 22:25:59 UTC 
How should this appear in the docs?

a)
/*
 * (*g_thread_gettime):
 * ...
 */
guint64 (*g_thread_gettime) (void);

b)
/*
 * g_thread_gettime:
 * ...
 */
guint64 g_thread_gettime (void);

I've checked in a fix that makes them appear as in version b). You should also add SCAN_OPTIONS=--ignore-decorators="GLIB_VAR" to you Makefile.am

2007-09-18  Stefan Kost  <ensonic@users.sf.net>

	* gtkdoc-scan.in:
	  Handle function pointers. Fixes #477532.
Comment 3 Matthias Clasen 2007-09-18 02:48:40 UTC 
Thanks. For my purposes, it is enough it gtk-doc doesn't fall over while parsing such constructs. The variable is not going to appear in the docs anyway.