You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
status RESOLVED severity minor in component general for ---
Reported in version 1.8.8 on platform Other
Assigned to: Dimitri van Heesch
On 2016-12-01 21:59:58 +0000, Michel Megens wrote:
Problem description
Having (double) underscores at both ends of a parameter name is parsed wrongly by doxygen. As far as I can tell from the warning messages it is actually interpreting that the underscores as 'bold text'.
Possible solutions
A possible solution would be to turn of any form of markup language parsing for the first argument to the @param tag. Which is something you probably want anyway.
Warnings generated by doxygen
The following warnings were spit out by doxygen:
warning: argument 'strong' of command @param is not found in the argument list of fs_split_path(const char *path)
warning: argument 'path' of command @param is not found in the argument list of fs_split_path(const char *path)
warning: argument 'strong' of command @param is not found in the argument list of fs_split_path(const char *path)
warning: The following parameters of fs_split_path(const char *path) are not documented:
On 2017-01-08 09:25:37 +0000, Dimitri van Heesch wrote:
Confirmed. Should be fixed in the next GIT update.
On 2017-12-25 18:43:39 +0000, Dimitri van Heesch wrote:
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.14. Please verify if this is indeed the case. Reopen the
bug if you think it is not fixed and please include any additional information
that you think can be relevant (preferably in the form of a self-contained example).
The text was updated successfully, but these errors were encountered:
status RESOLVED severity minor in component general for ---
Reported in version 1.8.8 on platform Other
Assigned to: Dimitri van Heesch
On 2016-12-01 21:59:58 +0000, Michel Megens wrote:
On 2017-01-08 09:25:37 +0000, Dimitri van Heesch wrote:
On 2017-12-25 18:43:39 +0000, Dimitri van Heesch wrote:
The text was updated successfully, but these errors were encountered: