New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

\endinternal issues warnings (Origin: bugzilla #674856) #4684

doxygen opened this Issue Jul 2, 2018 · 0 comments


None yet
1 participant

doxygen commented Jul 2, 2018

status RESOLVED severity normal in component general for ---
Reported in version 1.8.0 on platform Other
Assigned to: Dimitri van Heesch

Original attachment names and IDs:

On 2012-04-26 09:25:55 +0000, wrote:

The use of \endinternal issues warnings like

/home/dateien/projekte/agentxcpp/src/oid.hpp:119: warning: found \endinternal without matching \internal

Note that the command \endinternal works as expected, except of the warning.

On 2012-08-25 22:22:32 +0000, Steve Pucci wrote:

I'm seeing this all the time too. Here's an example standalone .md file which demonstrates it:

My Section Header

This is common text.

This is internal-only text.

This is common text too.

doxygen doxygen-cfg
/Users/spucci/doxy/endinternalbug/ warning: found \endinternal without matching \internal

On 2012-10-22 16:19:01 +0000, Passer Ivan wrote:

Spotted this on 1.7, and then on 1.8.2. If INTERNAL_DOCS=YES then the lex script does not enter the SKIP_INTERNAL state and thus gives a warning on the \endinternal command.
Quick solution would be to add the same if( INTERNAL_DOCS = NO) like at the \internal command mark in the script. Downside would be that if INTERNAL_DOCS=YES then it would just ignore the \endinternal and would not warn about actual mismatches.

On 2013-01-06 14:40:36 +0000, albert wrote:

Created attachment 232860
PATCH: Suppress \endinternal message

This patch suppresses the "warning: found \endinternal without matching \internal" in case INTERNAL_DOCS is set to YES.

On 2013-01-20 15:06:08 +0000, Dimitri van Heesch wrote:

Confirmed. Should be fixed in the next subversion update.

On 2013-05-19 12:36:52 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.4. 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.

On 2013-05-19 13:23:50 +0000, wrote:

I confirm that the problem is solved in doxygen 1.8.4. Thank you!

@doxygen doxygen closed this Jul 2, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment