# Bug report: Doxygen comments using \<summary\> causes wrong documentation

**URL:** <https://discourse.mcneel.com/t/bug-report-doxygen-comments-using-summary-causes-wrong-documentation/195987>\
**Category:** openNURBS\
**Tags:** windows, bug\
**Created:** [December 4, 2024, 2:02pm UTC](https://discourse.mcneel.com/t/bug-report-doxygen-comments-using-summary-causes-wrong-documentation/195987 "2024-12-04T14:02:13Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jakob\_van\_Bethlehem](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/jakob_van_bethlehem/32/563212_2.png) [@Jakob\_van\_Bethlehem](https://discourse.mcneel.com/u/Jakob_van_Bethlehem)\
**Post date:** [December 4, 2024, 2:02pm UTC](https://discourse.mcneel.com/t/bug-report-doxygen-comments-using-summary-causes-wrong-documentation/195987/1 "2024-12-04T14:02:13Z")

</div>

After some searching for a place to report bugs, and not finding it, I figured maybe posting in the forum would suffice as well.

While scanning and reading the online Doxygen-produced documentation at [Rhino C++ API: Main Page](https://developer.rhino3d.com/api/cpp/index.html) I kept noticing that sometimes documentation seems to be put on the wrong ‘topic’, usually being ‘one off’. Especially enum values seem to suffer from this.

Today I realized why: it is because each Doxygen comment uses the

# command to create the summary. Because this is written -immediately- after the /// . This results in Doxygen interpreting the first ‘\<’ as the ‘look-back-comment-operator’ . This is indeed clearly seen in the online output, where the literal word ‘summary\>’ is appearing in the output.

I guess it should be sufficient to go over each source and ensure there is at least one space between the ‘///’ and the ‘\<’