Skip to content

Conversation

@johnnonweiler
Copy link
Contributor

@johnnonweiler johnnonweiler commented Oct 12, 2018

Following on from #3115, this addresses some more of the warnings that are produced when running doxygen. (Note: Unlike the previous PR, these changes are not limited to changes to the documentation. For example, in some cases parameters have been renamed because doxygen couldn't cope with leading underscores.)

This PR addresses some of the issues in java_bytecode, goto-programs, util and cbmc.

Please see the individual commits for details.

  • Each commit message has a non-empty body, explaining why the change was made.
  • My contribution is formatted in line with CODING_STANDARD.md.
  • Methods or procedures I have added are documented, following the guidelines provided in CODING_STANDARD.md.
  • Regression or unit tests are included, or existing tests cover the modified code (in this case I have detailed which ones those are in the commit message).
  • My commit message includes data points confirming performance improvements (if claimed).
  • My PR is restricted to a single feature or bugfix.
  • White-space or formatting changes outside the feature-related changed lines are in commits of their own.

John Nonweiler added 6 commits October 12, 2018 16:37
Doxygen produces warnings if some parameters are documentated and not
others, or if there is documentation for parameters which don't exist.
Before this commit, get_xml_options had the parameters
"(const class xmlt &xml, cmdlinet &cmdline)" in the header file, and
"(const xmlt &xml, cmdlinet &cmdline)" in the cpp file.  Doxygen then
produced a warning "no matching class member found".  This commit
adds a forward declaration "class xmlt;" in the header file, so that
both versions of get_xml_options can have identical parameter lists.
Replace 'signed int' with 'int', and 'unsigned int' with 'unsigned',
so that .cpp and .h files are consistent, and doxygen doesn't get
confused
The doxygen comment in the header file was referring to a parameter
which was given a name only in the cpp file, and doxygen was complaining
that it could not find the parameter.
Doxygen doesn't seem to be able to handle method parameters such as
'_parameters' or '_return_type' properly.
Doxygen was warning that the argument 'type' has muliple @param
documentation sections, and producing incorrect documentation.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant