<p dir="ltr">No, this message comes from check-source, which is our own style (and other) checker. In-body refers to the body of the function, and I think this is the term used also in doxygen configuration. If there are no doxygen-formatted comments (e.g., starting with /** or ///), then something is tricking doxygen parser to see such things (or there can be a bug in the checker, but I'd first see what doxygen actually thinks is in the file).</p>
<p dir="ltr">You can run the doxygen-xml target locally and check the xml files to see what it thinks is an in-body comment, or you can add some debug prints to the docs/doxygen/check-source.py.</p>
<p dir="ltr">Teemu</p>
<p dir="ltr"></p>
<p dir="ltr">On Wed, Sep 2, 2015, 15:27 Mark Abraham <<a href="mailto:mark.j.abraham@gmail.com">mark.j.abraham@gmail.com</a>> wrote:</p>
<blockquote><p dir="ltr">Hi,<br></p>
<p dir="ltr">I think the message is confusing ("in body" refers to the body of the file?), but is caused by the fact that there is no file-level Doxygen markup in tpi.cpp, so Doxygen has nowhere to put the docs. I suggest adapting e.g. that of mdrun_signalling.cpp<br></p>
<p dir="ltr">Mark<br></p>
<p dir="ltr">On Wed, Sep 2, 2015 at 10:33 AM David van der Spoel <<a href="mailto:spoel@xray.bmc.uu.se">spoel@xray.bmc.uu.se</a>> wrote:</p>
</blockquote>
<blockquote><blockquote><p dir="ltr">Hi,</p>
<p dir="ltr">I'm stuck with a doxygen problem<br>
has in-body comments, which are ignored</p>
<p dir="ltr">the source file/routine in question does have normal comments /* bla bla<br>
*/ but that should be fine, right?</p>
<p dir="ltr">The problem appeared after I moved a function into the gmx namespace.<br>
This is the affected patch<br>
<a href="https://gerrit.gromacs.org/#/c/4734/">https://gerrit.gromacs.org/#/c/4734/</a></p>
<p dir="ltr">Any clues how to work around it?<br>
</p>
</blockquote>
</blockquote>