i've tried searching stackoverflow , users mailing list in official website not found useful problem, there lot of results unrelated...
doxygen used version 1.8.5.
i prefer style member function declaration this, let's call const-at-another-line style.
returntype functionname() const; i know people use all-in-same-line style,
returntype functionname() const; or return-type-at-another-line style
returntype functionname() const; for both all-in-same-line style , return-type-at-another-line style, doxygen can parse correctly.
however document of const-at-another-line style results in member data called "const" , type returntype.
class signal : public interface { bool hassignal() const; }; document shows class signal has public attributes
bool const and detailed documentation in member data documentations shows
bool signal::const i've tried these cases, pure virtual function:
bool hassignal() const =0; result in
bool signal::const =0 and c++11 final/override keyword: (i'm not expecting doxygen support c++11 syntax yet, comparison)
bool hassignal() const override; results in public attributes
bool const override which "const" link member data documentation in class interface
virtual bool interface::const = 0 and "override" link member data documentation in class signal
bool const signal::override my problem is: there config in doxygen missed can parse/document const member function using const-at-another-line style correctly? or can modify style fit doxygen document purpose?
looks has been fixed in version 1.8.6 , later (note version 1.8.5 released in august 2013 rather old). latest version of writing 1.8.9.1.
Comments
Post a Comment