GNOME Bugzilla – Bug 728285
docs: Use markdown links in .h files, too
Last modified: 2014-04-15 20:23:17 UTC
Commit e7fd3de86d60 already did this for all .c files. This patch does not change the links to 'extending-gio' as these links are broken since long and changing them to markdown would result in no visible links and hide this problem.
Created attachment 274391 [details] [review] docs: Use markdown links in .h files, too
Created attachment 274393 [details] [review] my patch Hmm, I have a patch that overlaps with yours - maybe you could merge the two and commit it all in one go ?
OK, but there are more <!-- comments still, how can these be fixed? Seems like plurals are recognized automatically(?) but what about @t_n<!-- -->_parent_class ? ./gclosure.h:105: * #GValue<!-- -->s holding the arguments on which to invoke the ./gtypemodule.h:94: * @t_n<!-- -->_parent_class pointing to the parent class. Furthermore, ./gtype.h:929: * Returns: %TRUE to stop further #GTypeClassCacheFunc<!-- -->s from being ./gtype.h:1320: * these) and a static variable named @t_n<!-- -->_parent_class pointing to the parent class. Furthermore, it defines ./gtype.h:1350: * these), a static variable named @t_n<!-- -->_parent_class pointing to the parent class, and adds private ./gvaluecollector.h:247: * The maximal number of #GTypeCValue<!-- -->s which can be collected for a ./gclosure.c:54: * other languages need marshallers which convert between #GValue<!--
(Accidentally just greped in a subdir above, btw, but there are just a few more <!-- comments all in all)
Created attachment 274399 [details] [review] docs: Use markdown links in .h files, too Commit e7fd3de86d60 already did this for all .c files.
(In reply to comment #5) Included the [Extending GIO][extending-gio] links too now (though they are still broken and don't show up in the html (bug 728283). I think dealing with the <!-- comments should go in another commit once we decide on how to deal with the @t_n<!-- -->_parent_class stuff?
(In reply to comment #6) > (In reply to comment #5) > Included the [Extending GIO][extending-gio] links too now (though they are > still broken and don't show up in the html (bug 728283). > > I think dealing with the <!-- comments should go in another commit once we > decide on how to deal with the @t_n<!-- -->_parent_class stuff? I agree. A separate commit for that is better
Review of attachment 274399 [details] [review]: Looks good