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
Actually you add the @protected and @private commands if the function has an single underscore _ respectively double underscore __.
The interpretation of the underscores is correct but doxygen will ignore them if the language is object-oriented:
\protected
Indicates that the member documented by the comment block is protected, i.e., should only be accessed by other members in the same or derived classes.
Note that Doxygen automatically detects the protection level of members in object-oriented languages. This command is intended for use only when the language does not support the concept of protection level natively (e.g. C, PHP 4).
(same for private)
doxygen actually mark everything as private which begins with one or more underscore.
Of course you can nothing do to change that, I want to only leave this information here for users which are confused (and that you do not have to add the @protected and @private commands).
I opened an issue so that it will be corrected.
The text was updated successfully, but these errors were encountered:
Yeah, over the years a few other similar issues have been raised but there's not too much we can do about them. Our policy has been to make doxypypy send the best data that it can even knowing it may be ignored by the current version of Doxygen. If at some point that data gets considered we'll be ready.
Actually you add the
@protected
and@private
commands if the function has an single underscore_
respectively double underscore__
.The interpretation of the underscores is correct but doxygen will ignore them if the language is object-oriented:
(same for private)
doxygen actually mark everything as private which begins with one or more underscore.
Of course you can nothing do to change that, I want to only leave this information here for users which are confused (and that you do not have to add the
@protected
and@private
commands).I opened an issue so that it will be corrected.
The text was updated successfully, but these errors were encountered: