-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
unexpected token TK_COMMAND_BS as the argument of \ifile #10937
Comments
Indeed the core problem is the test.h
test.doc
I used here The fact that we don't get a warning for the So in fact we have multiple problems:
|
… `\ifile` From a tag file it is possible that detailed section is set but that no file name is included. The file `file` of `DocInfo` etc. is always present when the `DocInfo` is present, it is better to test whether the field is empty or not.
Regarding the warning problem I've just pushed a proposed patch, pull request #10939 |
… `\ifile` In case a reference for `\copy...` is coming from a tag file there is no information present and this was not reported.
Regarding the fact that |
issue #10937 unexpected token TK_COMMAND_BS as the argument of `\ifile`
issue #10937 unexpected token TK_COMMAND_BS as the argument of `\ifile`
Code of both pull requests has been integrated in master on GitHub (please don't close the issue as this will be done at the moment of an official release). |
Describe the bug
Screenshots
To Reproduce
call:
doxygen Doxyfile.tag
and thandoxygen Doxyfile.bug-1
Expected behavior
this depends… the core-problem is a @copydetails from a
tagfile
group targetVersion
Doxygen version used: 1.10.0 (ebc57c6)
Linux linux02 5.14.21-150500.55.65-default #1 SMP PREEMPT_DYNAMIC Thu May 23 04:57:11 UTC 2024 (a46829d) x86_64 x86_64 x86_64 GNU/Linux
Additional context
Attachment → doxygen_bug__unexpected_token_TK_COMMAND_BS.tar.gz
The text was updated successfully, but these errors were encountered: