diff options
| author | albert-github <albert.tests@gmail.com> | 2015-11-08 18:27:15 (GMT) |
|---|---|---|
| committer | Dimitri van Heesch <dimitri@stack.nl> | 2015-11-22 13:00:35 (GMT) |
| commit | 8504fc3a06e3430242eab9ac1c1f20319112e6a9 (patch) | |
| tree | 8213543a78b8bf26770f3c77b220f2e38503531e /examples/example.cpp | |
| parent | 12f6f4faf541116295dcd69958e476ec32150a64 (diff) | |
| download | Doxygen-8504fc3a06e3430242eab9ac1c1f20319112e6a9.zip Doxygen-8504fc3a06e3430242eab9ac1c1f20319112e6a9.tar.gz Doxygen-8504fc3a06e3430242eab9ac1c1f20319112e6a9.tar.bz2 | |
Fortran module private variables and EXTRACT_PRIVATE = NO
From the message in the doxygen forum(http://doxygen.10944.n7.nabble.com/Fortan-problems-td7434.html and http://doxygen.10944.n7.nabble.com/Fortran-module-private-variables-and-EXTRACT-PRIVATE-NO-td7423.html)
B. If EXTRACT_PRIVATE = NO, module private functions are not listed (as expected) but module private variables are (bug!).
C. Implicit PRIVATE/PUBLIC/PROTECTED statements in a module work as expected but are not "appended" to function/variable documentation. This is only a nuisance.
Problem had a common cause, the protection was hard set to 'Public' instead of the read value (analogous to static)
Diffstat (limited to 'examples/example.cpp')
0 files changed, 0 insertions, 0 deletions