doc : define the __parser__
attribute related to doxygen integration …
More...
Macros | |
#define | __parser__doc_group doc-group@OVERWRITE=DOC |
Use the doc-group section in the doxygen documentation … | |
#define | __parser__doc_index doc-index=INDEX |
Add index doc-index to the doc-group section … | |
#define | __parser__doc_name doc-name=NAME |
Add name doc-name section to the doc-group section … | |
#define | __parser__doc_no doc-no |
Do not write a doc entry into the doxygen documentation … | |
#define | __parser__global__doc_force doc-force@LIST=CLASS_or_PACKAGE@INDEX@?local? |
Force the doyygen-index to be build even if no function is available … | |
#define | __parser__global__doc_db doc-db=DIRECTORY |
Set directory for external documentation lookup… | |
#define | __parser__doc_sort doc-sort=DICTIONARY |
dictionary doc-sort of the function in the documantation… | |
doc : define the __parser__
attribute related to doxygen integration …
Define the __parser__(doc-XXX=…) function…
, __parser__global__(function:doc-XXX:…)
or the __parser__global__(function:…)
attribute.
The doc-attribute is used to integrate the All-Language-Compiler (ALC) code into the doxygen-documentation.
The documentation is splitted into 3 parts called doc-index, doc-group and doc-name:
_ignore_
value. Misc
value. [A-Z][a-zA-Z0-9]
.The doc-attribute create a doxygen-item:
The following restrictions are used by the doc-attribute:
_ignore_
the doxygen-item disappears. _ignore_
the doxygen-section is set to MyClass_?MyIndex?_MyGroup_LNG_Api - ...
The C
__parser__ extension does not read the already available doxygen documentation and doc-index and doc-group have to fit into the existing doxygen structure.
example: the doc-attribute integration into doxygen with manually added code:
example: the overload-feature (c_Overload.tcl
) create the following code for the MkErrorNext function:
#define __parser__doc_group doc-group@OVERWRITE=DOC |
Use the doc-group section in the doxygen documentation …
Every function is added to a doc-group section, if no doc-group section is set the default Misc
is used.
Misc
value use the _ignore_
value. scope | global or function |
usage | __parser__global__(FUNCTION:doc-group=DOC); |
usage | __parser__(doc-group=DOC) FUNCTION ... |
see also | __parser__(doc-no); __parser__(doc-index) |
Definition at line 1977 of file parser_mk.h.
#define __parser__doc_index doc-index=INDEX |
Add index doc-index to the doc-group section …
Sometimes there are too many functions in a class for a clear presentation. With the doc-index it is possible to add an additional index-level.
The doc-index is created ONLY when a function is available. If you want the doc-index to always be created, use the global doc-force option such as __parser__global__(doc-force=MyClass@MyIndex);
.
_ignore_
(the default value) than the doc-group with default value Misc
is used. scope | global or function |
usage | __parser__global__(FUNCTION:doc-index:INDEX); |
usage | __parser__(doc-index=INDEX) FUNCTION ... |
see also | doc-group; doc-name; doc-no |
Definition at line 1999 of file parser_mk.h.
#define __parser__doc_name doc-name=NAME |
Add name doc-name section to the doc-group section …
Sometimes a function should be added to the main-doc-class like MkBufferC_C_API
, but in a separate namespace to group the functions together or to improve readability.
@name
section to the documentation If the All-Language-Compiler (ALC) decides to add a @name
section, for example to summarize the inline
or overload
functions, doc-name is the default-name. With _ignore_
the doc-group is used like MyClassC_MyGroup_C_API
.
scope | global or function |
usage | __parser__global__(FUNCTION:doc-name:NAME); |
usage | __parser__(doc-name=NAME) FUNCTION ... |
see also | doc-group; doc-index; doc-no |
Definition at line 2018 of file parser_mk.h.
#define __parser__doc_no doc-no |
Do not write a doc entry into the doxygen documentation …
The doc-no feature is usefull if an internal or hidden function is visible to the public-api but only for testing purpose.
scope | global or function |
usage | __parser__global__(FUNCTION:doc-no=yes); |
usage | __parser__(doc-no) FUNCTION ... |
see also | doc-group; doc-index |
Definition at line 2043 of file parser_mk.h.
#define __parser__doc_sort doc-sort=DICTIONARY |
dictionary doc-sort of the function in the documantation…
All function belonging to a group ar sorted regarding the doc-sort. If the doc-sort is not set then an order is created. by default the character-set-sort-order (TCL: lsort -ascii) is used.
usage | __parser__global__(doc-sort=DICTIONARY); |
example | __parser__global__(doc-sort=ils-2); |
see also | doc-group; doc-index |
Definition at line 2120 of file parser_mk.h.
#define __parser__global__doc_db doc-db=DIRECTORY |
Set directory for external documentation lookup…
This attribute is only used if a native library without PLMK (Programming-Language-Micro-Kernel)-Support is used as input and the native documentation-format can not be used by doxygen.
The external-documentation of a native-library is using usually an other documentation-format as doxygen.
A documentation-preprocessor have to be written for any external documentation and is required to transfer the external-documentation into a format readable by doxygen.
Finally the external-documentation put into the doc-db database and a All-Language-Compiler (ALC) tool like c_NativeDoc.tcl
is used to build the final doxygen documentation.
libconfig_2_docdb.tcl
is part of the LibLcConfig package. libsqlite3_2_docdb.tcl
is part of the LibSq3Lite package.The format of the documentation-database is easy, a directory with a file for every documentation item.
usage | __parser__global__(doc-db=DIRECTORY); |
example | __parser__global__(doc-db=doc_db.dir); |
see also | MkKernel_Parser_Doc_C_API |
Definition at line 2107 of file parser_mk.h.
#define __parser__global__doc_force doc-force@LIST=CLASS_or_PACKAGE@INDEX@?local? |
Force the doyygen-index to be build even if no function is available …
The __parser__(doc-index=MyDocIndex);
will ONLY be build if a function is available. If the build should always be done use the __parser__global__(doc-force=MyClass@MyDocIndex);
global option. If the optional third option is the string local
than a local-reference will be used as source of documentation like ${class}_${doc(R)}_${lng}_API
rather than ${class}_${doc(R)}_C_API
. A local-reference is usefull if the Target-Programming-Language (TPL) language documentation differ.
usage | __parser__global__(doc-force=CLASS_or_PACKAGE@INDEX@?local?); |
example | __parser__global__(doc-force=MqMsgque@Item); |
see also | doc-group; doc-index |
Definition at line 2059 of file parser_mk.h.