Hi, Helmut Grohne wrote: > As for the libburn maintainers, I suggest to change the comment in the > header to not include the verbatim string "burn_abort(>0)" in order to > not confuse doxygen.
Done by http://www.libburnia-project.org/changeset/5122 Do you have more advise for me ? E.g. for this snippet from the message log: > /«PKGBUILDDIR»/libburn/libburn.h:3515: Warning: explicit link request to 'if' > could not be resolved In my source of libburn-1.2.2, line 3515 is the last one of ------------------------------------------------------------------------ /** Control queueing and stderr printing of messages from libburn. Severity may be one of "NEVER", "ABORT", "FATAL", "FAILURE", "SORRY", "WARNING", "HINT", "NOTE", "UPDATE", "DEBUG", "ALL". @param queue_severity Gives the minimum limit for messages to be queued. Default: "NEVER". If you queue messages then you must consume them by burn_msgs_obtain(). @param print_severity Does the same for messages to be printed directly to stderr. Default: "FATAL". @param print_id A text prefix to be printed before the message. @return >0 for success, <=0 for error @since 0.2.6 */ int burn_msgs_set_severities(char *queue_severity, char *print_severity, char *print_id); ------------------------------------------------------------------------ What am i doing wrong ? I do not send this to doxygen-deve...@lists.sourceforge.net because i expect them to be interested in bug fixing and not in user education. Have a nice day :) Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
