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

Warning: Illegal command 123 as part of a \ref in generated todo list (Origin: bugzilla #427012) #2445

Closed
doxygen opened this Issue Jul 1, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@doxygen
Owner

doxygen commented Jul 1, 2018

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

On 2007-04-06 18:36:22 +0000, James Dennett wrote:

With a default Doxyfile, the following C++ source file generated an error
todo:1: Warning: Illegal command 0 as part of a \ref

Here's the source file to reproduce this with Doxygen 1.5.1:
/**

  • @todo Fix this bug
    */
    namespace {}

I see other issues in bugzilla about issues with anonymous namespaces, but could not find this one. When time permits I will try to check this against 1.5.2 or against the latest source code.

On 2013-01-22 19:07:36 +0000, albert wrote:

A similar message still occurs in version 1.5.2, message is:
todo:1: Warning: Illegal command 0 as part of a \ref
The messages does not appear in version 1.8.3.1
The html output the line in the to do list reads:
Namespace @0@0

So the original "problem" does not exist but I don't think the line in the todo page is correct.

On 2013-02-23 10:04:48 +0000, Dimitri van Heesch wrote:

I'll remove the bogus entry.

On 2013-05-19 12:35:22 +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.

@doxygen doxygen closed this Jul 1, 2018

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