You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
status ASSIGNED severity normal in component general for ---
Reported in version 1.8.6 on platform Other
Assigned to: Dimitri van Heesch
On 2014-03-26 17:13:11 +0000, Daniel Sheridan wrote:
I found a function missing from a call graph in a large third-party code
base. I've traced the issue to an oddly formatted comment to produce this
minimal example:
/*///*/
void c() {
c();
}
void main() {
c();
}
With the three slashes in the comment, no callgraph is generated for c() or
main(). With two slashes (i.e., /*//*/), the callgraphs are generated as
expected.
The following also fails: /* random text ///*/
While this succeeds: /*/// */
On 2014-03-26 17:13:42 +0000, Daniel Sheridan wrote:
I should add that this is C++.
On 2018-05-12 17:02:12 +0000, albert wrote:
In the current version (1.8.14) we get the warning:
aa.cpp:14: warning: Reached end of file while still inside a (nested)
comment. Nesting level 2 (probable line reference: 3, 3)
(I added 2 lines at the beginning of the file.)
In version 1.8.6 this message is not given.
In the string we see the start of the nested comment:
/*///*/
^ start of the nested comment.
It strongly advised to fix this warning (also upstream in the third-party
software / inform that party about it).
When we look at the code coloring (SOURCE_BROWSER = YES,
STRIP_CODE_COMMENTS=NO we see also that the functions are in the comment
color)
I've just pushed a proposed patch to github (pull request 721,
https://github.com/doxygen/doxygen/pull/721).
On 2018-06-27 10:33:39 +0000, albert wrote:
2018/06/24 Code has been integrated in master on github.
The text was updated successfully, but these errors were encountered:
This issue was previously marked 'fixed but not released',
which means it should be fixed in doxygen version 1.8.16.
Please verify if this is indeed the case. Reopen the
issue if you think it is not fixed and please include any additional information
that you think can be relevant (preferably in the form of a self-contained example).
status ASSIGNED severity normal in component general for ---
Reported in version 1.8.6 on platform Other
Assigned to: Dimitri van Heesch
On 2014-03-26 17:13:11 +0000, Daniel Sheridan wrote:
On 2014-03-26 17:13:42 +0000, Daniel Sheridan wrote:
On 2018-05-12 17:02:12 +0000, albert wrote:
On 2018-06-27 10:33:39 +0000, albert wrote:
The text was updated successfully, but these errors were encountered: