diff options
| author | albert-github <albert.tests@gmail.com> | 2015-11-08 18:27:15 (GMT) |
|---|---|---|
| committer | albert-github <albert.tests@gmail.com> | 2015-11-08 18:27:15 (GMT) |
| commit | 61820a08200ec62c754cacf8dd3a1121ce6dee69 (patch) | |
| tree | c35dbab1d285ae11cbed0176469f7a79fff51442 /examples/example.cpp | |
| parent | e2dd83527381c67d38434e5cf1348f2a94887500 (diff) | |
| download | Doxygen-61820a08200ec62c754cacf8dd3a1121ce6dee69.zip Doxygen-61820a08200ec62c754cacf8dd3a1121ce6dee69.tar.gz Doxygen-61820a08200ec62c754cacf8dd3a1121ce6dee69.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