From 667c94d4c814daec165a23fb251a7c38f37e202d Mon Sep 17 00:00:00 2001 From: Karl Berry Date: Fri, 27 Jul 2012 23:39:36 +0000 Subject: new support package lua2dox (20jul12) git-svn-id: svn://tug.org/texlive/trunk@27205 c570f23f-e606-0410-a88d-b1316a301751 --- Master/bin/alpha-linux/lua2dox_filter | 1 + Master/bin/alpha-linux/lua2dox_lua | 1 + Master/bin/amd64-freebsd/lua2dox_filter | 1 + Master/bin/amd64-freebsd/lua2dox_lua | 1 + Master/bin/amd64-kfreebsd/lua2dox_filter | 1 + Master/bin/amd64-kfreebsd/lua2dox_lua | 1 + Master/bin/armel-linux/lua2dox_filter | 1 + Master/bin/armel-linux/lua2dox_lua | 1 + Master/bin/i386-cygwin/lua2dox_filter | 1 + Master/bin/i386-cygwin/lua2dox_lua | 1 + Master/bin/i386-freebsd/lua2dox_filter | 1 + Master/bin/i386-freebsd/lua2dox_lua | 1 + Master/bin/i386-kfreebsd/lua2dox_filter | 1 + Master/bin/i386-kfreebsd/lua2dox_lua | 1 + Master/bin/i386-linux/lua2dox_filter | 1 + Master/bin/i386-linux/lua2dox_lua | 1 + Master/bin/i386-solaris/lua2dox_filter | 1 + Master/bin/i386-solaris/lua2dox_lua | 1 + Master/bin/mipsel-linux/lua2dox_filter | 1 + Master/bin/mipsel-linux/lua2dox_lua | 1 + Master/bin/powerpc-aix/lua2dox_filter | 1 + Master/bin/powerpc-aix/lua2dox_lua | 1 + Master/bin/powerpc-linux/lua2dox_filter | 1 + Master/bin/powerpc-linux/lua2dox_lua | 1 + Master/bin/sparc-solaris/lua2dox_filter | 1 + Master/bin/sparc-solaris/lua2dox_lua | 1 + Master/bin/universal-darwin/lua2dox_filter | 1 + Master/bin/universal-darwin/lua2dox_lua | 1 + Master/bin/x86_64-darwin/lua2dox_filter | 1 + Master/bin/x86_64-darwin/lua2dox_lua | 1 + Master/bin/x86_64-linux/lua2dox_filter | 1 + Master/bin/x86_64-linux/lua2dox_lua | 1 + Master/bin/x86_64-solaris/lua2dox_filter | 1 + Master/bin/x86_64-solaris/lua2dox_lua | 1 + Master/texmf-dist/doc/support/lua2dox/Doxyfile | 1422 ++++++++++++++++++++ Master/texmf-dist/doc/support/lua2dox/INSTALL | 42 + Master/texmf-dist/doc/support/lua2dox/README | 17 + .../doc/support/lua2dox/docs/html/doxygen.css | 473 +++++++ .../doc/support/lua2dox/docs/html/doxygen.png | Bin 0 -> 1281 bytes .../doc/support/lua2dox/docs/html/files.html | 31 + .../doc/support/lua2dox/docs/html/globals.html | 92 ++ .../support/lua2dox/docs/html/globals_func.html | 92 ++ .../doc/support/lua2dox/docs/html/index.html | 43 + .../lua2dox/docs/html/lua2dox_8lua-source.html | 638 +++++++++ .../support/lua2dox/docs/html/lua2dox_8lua.html | 891 ++++++++++++ .../doc/support/lua2dox/docs/html/tab_b.gif | Bin 0 -> 35 bytes .../doc/support/lua2dox/docs/html/tab_l.gif | Bin 0 -> 706 bytes .../doc/support/lua2dox/docs/html/tab_r.gif | Bin 0 -> 2585 bytes .../doc/support/lua2dox/docs/html/tabs.css | 102 ++ .../doc/support/lua2dox/examples/lua/Doxyfile | 1421 +++++++++++++++++++ .../doc/support/lua2dox/examples/lua/animals.lua | 120 ++ .../doc/support/lua2dox/examples/lua/class.lua | 85 ++ .../lua/docs/html/animals_8lua-source.html | 141 ++ .../examples/lua/docs/html/animals_8lua.html | 113 ++ .../lua2dox/examples/lua/docs/html/annotated.html | 39 + .../lua/docs/html/classAnimal-members.html | 34 + .../examples/lua/docs/html/classAnimal.html | 151 +++ .../lua2dox/examples/lua/docs/html/classAnimal.png | Bin 0 -> 733 bytes .../examples/lua/docs/html/classBird-members.html | 34 + .../lua2dox/examples/lua/docs/html/classBird.html | 87 ++ .../lua2dox/examples/lua/docs/html/classBird.png | Bin 0 -> 498 bytes .../examples/lua/docs/html/classCat-members.html | 34 + .../lua2dox/examples/lua/docs/html/classCat.html | 84 ++ .../lua2dox/examples/lua/docs/html/classCat.png | Bin 0 -> 346 bytes .../examples/lua/docs/html/classDog-members.html | 34 + .../lua2dox/examples/lua/docs/html/classDog.html | 84 ++ .../lua2dox/examples/lua/docs/html/classDog.png | Bin 0 -> 351 bytes .../lua/docs/html/classMammal-members.html | 34 + .../examples/lua/docs/html/classMammal.html | 87 ++ .../lua2dox/examples/lua/docs/html/classMammal.png | Bin 0 -> 461 bytes .../lua/docs/html/classPigeon-members.html | 34 + .../examples/lua/docs/html/classPigeon.html | 84 ++ .../lua2dox/examples/lua/docs/html/classPigeon.png | Bin 0 -> 343 bytes .../lua/docs/html/classRedKite-members.html | 34 + .../examples/lua/docs/html/classRedKite.html | 84 ++ .../examples/lua/docs/html/classRedKite.png | Bin 0 -> 354 bytes .../examples/lua/docs/html/class_8lua-source.html | 106 ++ .../lua2dox/examples/lua/docs/html/class_8lua.html | 79 ++ .../lua2dox/examples/lua/docs/html/doxygen.css | 473 +++++++ .../lua2dox/examples/lua/docs/html/doxygen.png | Bin 0 -> 1281 bytes .../lua2dox/examples/lua/docs/html/files.html | 34 + .../lua2dox/examples/lua/docs/html/functions.html | 52 + .../examples/lua/docs/html/functions_func.html | 52 + .../lua2dox/examples/lua/docs/html/globals.html | 45 + .../examples/lua/docs/html/globals_func.html | 45 + .../lua2dox/examples/lua/docs/html/hierarchy.html | 45 + .../lua2dox/examples/lua/docs/html/index.html | 25 + .../examples/lua/docs/html/main_8lua-source.html | 63 + .../lua2dox/examples/lua/docs/html/main_8lua.html | 35 + .../lua2dox/examples/lua/docs/html/tab_b.gif | Bin 0 -> 35 bytes .../lua2dox/examples/lua/docs/html/tab_l.gif | Bin 0 -> 706 bytes .../lua2dox/examples/lua/docs/html/tab_r.gif | Bin 0 -> 2585 bytes .../lua2dox/examples/lua/docs/html/tabs.css | 102 ++ .../doc/support/lua2dox/examples/lua/main.lua | 42 + .../doc/support/lua2dox/examples/php/Doxyfile | 1421 +++++++++++++++++++ .../doc/support/lua2dox/examples/php/animals.php | 100 ++ .../php/docs/html/animals_8php-source.html | 104 ++ .../examples/php/docs/html/animals_8php.html | 113 ++ .../lua2dox/examples/php/docs/html/annotated.html | 39 + .../php/docs/html/classAnimal-members.html | 34 + .../examples/php/docs/html/classAnimal.html | 135 ++ .../lua2dox/examples/php/docs/html/classAnimal.png | Bin 0 -> 733 bytes .../examples/php/docs/html/classBird-members.html | 35 + .../lua2dox/examples/php/docs/html/classBird.html | 81 ++ .../lua2dox/examples/php/docs/html/classBird.png | Bin 0 -> 498 bytes .../examples/php/docs/html/classCat-members.html | 35 + .../lua2dox/examples/php/docs/html/classCat.html | 80 ++ .../lua2dox/examples/php/docs/html/classCat.png | Bin 0 -> 346 bytes .../examples/php/docs/html/classDog-members.html | 35 + .../lua2dox/examples/php/docs/html/classDog.html | 80 ++ .../lua2dox/examples/php/docs/html/classDog.png | Bin 0 -> 351 bytes .../php/docs/html/classMammal-members.html | 34 + .../examples/php/docs/html/classMammal.html | 54 + .../lua2dox/examples/php/docs/html/classMammal.png | Bin 0 -> 461 bytes .../php/docs/html/classPigeon-members.html | 36 + .../examples/php/docs/html/classPigeon.html | 80 ++ .../lua2dox/examples/php/docs/html/classPigeon.png | Bin 0 -> 343 bytes .../php/docs/html/classRedKite-members.html | 36 + .../examples/php/docs/html/classRedKite.html | 80 ++ .../examples/php/docs/html/classRedKite.png | Bin 0 -> 354 bytes .../lua2dox/examples/php/docs/html/doxygen.css | 473 +++++++ .../lua2dox/examples/php/docs/html/doxygen.png | Bin 0 -> 1281 bytes .../lua2dox/examples/php/docs/html/files.html | 33 + .../lua2dox/examples/php/docs/html/functions.html | 56 + .../examples/php/docs/html/functions_func.html | 56 + .../lua2dox/examples/php/docs/html/globals.html | 46 + .../examples/php/docs/html/globals_func.html | 44 + .../examples/php/docs/html/globals_vars.html | 42 + .../lua2dox/examples/php/docs/html/hierarchy.html | 45 + .../lua2dox/examples/php/docs/html/index.html | 25 + .../examples/php/docs/html/main_8php-source.html | 51 + .../lua2dox/examples/php/docs/html/main_8php.html | 63 + .../lua2dox/examples/php/docs/html/tab_b.gif | Bin 0 -> 35 bytes .../lua2dox/examples/php/docs/html/tab_l.gif | Bin 0 -> 706 bytes .../lua2dox/examples/php/docs/html/tab_r.gif | Bin 0 -> 2585 bytes .../lua2dox/examples/php/docs/html/tabs.css | 102 ++ .../doc/support/lua2dox/examples/php/main.php | 44 + Master/texmf-dist/doc/support/lua2dox/install.sh | 73 + .../doc/support/lua2dox/lua2dox-refm.pdf | Bin 0 -> 389213 bytes .../doc/support/lua2dox/lua2dox-refm.tex | 416 ++++++ Master/texmf-dist/scripts/lua2dox/lua.def | 39 + Master/texmf-dist/scripts/lua2dox/lua2dox.lua | 618 +++++++++ Master/texmf-dist/scripts/lua2dox/lua2dox_lua | 86 ++ Master/tlpkg/bin/tlpkg-ctan-check | 3 +- Master/tlpkg/libexec/ctan2tds | 51 +- Master/tlpkg/tlpsrc/collection-luatex.tlpsrc | 1 + Master/tlpkg/tlpsrc/lua2dox.tlpsrc | 2 + 147 files changed, 12853 insertions(+), 21 deletions(-) create mode 120000 Master/bin/alpha-linux/lua2dox_filter create mode 120000 Master/bin/alpha-linux/lua2dox_lua create mode 120000 Master/bin/amd64-freebsd/lua2dox_filter create mode 120000 Master/bin/amd64-freebsd/lua2dox_lua create mode 120000 Master/bin/amd64-kfreebsd/lua2dox_filter create mode 120000 Master/bin/amd64-kfreebsd/lua2dox_lua create mode 120000 Master/bin/armel-linux/lua2dox_filter create mode 120000 Master/bin/armel-linux/lua2dox_lua create mode 120000 Master/bin/i386-cygwin/lua2dox_filter create mode 120000 Master/bin/i386-cygwin/lua2dox_lua create mode 120000 Master/bin/i386-freebsd/lua2dox_filter create mode 120000 Master/bin/i386-freebsd/lua2dox_lua create mode 120000 Master/bin/i386-kfreebsd/lua2dox_filter create mode 120000 Master/bin/i386-kfreebsd/lua2dox_lua create mode 120000 Master/bin/i386-linux/lua2dox_filter create mode 120000 Master/bin/i386-linux/lua2dox_lua create mode 120000 Master/bin/i386-solaris/lua2dox_filter create mode 120000 Master/bin/i386-solaris/lua2dox_lua create mode 120000 Master/bin/mipsel-linux/lua2dox_filter create mode 120000 Master/bin/mipsel-linux/lua2dox_lua create mode 120000 Master/bin/powerpc-aix/lua2dox_filter create mode 120000 Master/bin/powerpc-aix/lua2dox_lua create mode 120000 Master/bin/powerpc-linux/lua2dox_filter create mode 120000 Master/bin/powerpc-linux/lua2dox_lua create mode 120000 Master/bin/sparc-solaris/lua2dox_filter create mode 120000 Master/bin/sparc-solaris/lua2dox_lua create mode 120000 Master/bin/universal-darwin/lua2dox_filter create mode 120000 Master/bin/universal-darwin/lua2dox_lua create mode 120000 Master/bin/x86_64-darwin/lua2dox_filter create mode 120000 Master/bin/x86_64-darwin/lua2dox_lua create mode 120000 Master/bin/x86_64-linux/lua2dox_filter create mode 120000 Master/bin/x86_64-linux/lua2dox_lua create mode 120000 Master/bin/x86_64-solaris/lua2dox_filter create mode 120000 Master/bin/x86_64-solaris/lua2dox_lua create mode 100644 Master/texmf-dist/doc/support/lua2dox/Doxyfile create mode 100644 Master/texmf-dist/doc/support/lua2dox/INSTALL create mode 100644 Master/texmf-dist/doc/support/lua2dox/README create mode 100644 Master/texmf-dist/doc/support/lua2dox/docs/html/doxygen.css create mode 100644 Master/texmf-dist/doc/support/lua2dox/docs/html/doxygen.png create mode 100644 Master/texmf-dist/doc/support/lua2dox/docs/html/files.html create mode 100644 Master/texmf-dist/doc/support/lua2dox/docs/html/globals.html create mode 100644 Master/texmf-dist/doc/support/lua2dox/docs/html/globals_func.html create mode 100644 Master/texmf-dist/doc/support/lua2dox/docs/html/index.html create mode 100644 Master/texmf-dist/doc/support/lua2dox/docs/html/lua2dox_8lua-source.html create mode 100644 Master/texmf-dist/doc/support/lua2dox/docs/html/lua2dox_8lua.html create mode 100644 Master/texmf-dist/doc/support/lua2dox/docs/html/tab_b.gif create mode 100644 Master/texmf-dist/doc/support/lua2dox/docs/html/tab_l.gif create mode 100644 Master/texmf-dist/doc/support/lua2dox/docs/html/tab_r.gif create mode 100644 Master/texmf-dist/doc/support/lua2dox/docs/html/tabs.css create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/lua/Doxyfile create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/lua/animals.lua create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/lua/class.lua create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/animals_8lua-source.html create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/animals_8lua.html create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/annotated.html create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classAnimal-members.html create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classAnimal.html create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classAnimal.png create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classBird-members.html create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classBird.html create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classBird.png create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classCat-members.html create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classCat.html create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classCat.png create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classDog-members.html create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classDog.html create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classDog.png create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classMammal-members.html create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classMammal.html create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classMammal.png create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classPigeon-members.html create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classPigeon.html create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classPigeon.png create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classRedKite-members.html create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classRedKite.html create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classRedKite.png create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/class_8lua-source.html create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/class_8lua.html create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/doxygen.css create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/doxygen.png create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/files.html create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/functions.html create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/functions_func.html create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/globals.html create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/globals_func.html create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/hierarchy.html create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/index.html create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/main_8lua-source.html create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/main_8lua.html create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/tab_b.gif create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/tab_l.gif create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/tab_r.gif create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/tabs.css create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/lua/main.lua create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/php/Doxyfile create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/php/animals.php create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/animals_8php-source.html create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/animals_8php.html create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/annotated.html create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classAnimal-members.html create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classAnimal.html create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classAnimal.png create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classBird-members.html create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classBird.html create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classBird.png create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classCat-members.html create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classCat.html create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classCat.png create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classDog-members.html create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classDog.html create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classDog.png create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classMammal-members.html create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classMammal.html create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classMammal.png create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classPigeon-members.html create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classPigeon.html create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classPigeon.png create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classRedKite-members.html create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classRedKite.html create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classRedKite.png create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/doxygen.css create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/doxygen.png create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/files.html create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/functions.html create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/functions_func.html create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/globals.html create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/globals_func.html create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/globals_vars.html create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/hierarchy.html create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/index.html create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/main_8php-source.html create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/main_8php.html create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/tab_b.gif create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/tab_l.gif create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/tab_r.gif create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/tabs.css create mode 100644 Master/texmf-dist/doc/support/lua2dox/examples/php/main.php create mode 100755 Master/texmf-dist/doc/support/lua2dox/install.sh create mode 100644 Master/texmf-dist/doc/support/lua2dox/lua2dox-refm.pdf create mode 100644 Master/texmf-dist/doc/support/lua2dox/lua2dox-refm.tex create mode 100755 Master/texmf-dist/scripts/lua2dox/lua.def create mode 100755 Master/texmf-dist/scripts/lua2dox/lua2dox.lua create mode 100755 Master/texmf-dist/scripts/lua2dox/lua2dox_lua create mode 100644 Master/tlpkg/tlpsrc/lua2dox.tlpsrc (limited to 'Master') diff --git a/Master/bin/alpha-linux/lua2dox_filter b/Master/bin/alpha-linux/lua2dox_filter new file mode 120000 index 00000000000..813f7749250 --- /dev/null +++ b/Master/bin/alpha-linux/lua2dox_filter @@ -0,0 +1 @@ +lua2dox_lua \ No newline at end of file diff --git a/Master/bin/alpha-linux/lua2dox_lua b/Master/bin/alpha-linux/lua2dox_lua new file mode 120000 index 00000000000..3dcc4b61c72 --- /dev/null +++ b/Master/bin/alpha-linux/lua2dox_lua @@ -0,0 +1 @@ +../../texmf-dist/scripts/lua2dox/lua2dox_lua \ No newline at end of file diff --git a/Master/bin/amd64-freebsd/lua2dox_filter b/Master/bin/amd64-freebsd/lua2dox_filter new file mode 120000 index 00000000000..813f7749250 --- /dev/null +++ b/Master/bin/amd64-freebsd/lua2dox_filter @@ -0,0 +1 @@ +lua2dox_lua \ No newline at end of file diff --git a/Master/bin/amd64-freebsd/lua2dox_lua b/Master/bin/amd64-freebsd/lua2dox_lua new file mode 120000 index 00000000000..3dcc4b61c72 --- /dev/null +++ b/Master/bin/amd64-freebsd/lua2dox_lua @@ -0,0 +1 @@ +../../texmf-dist/scripts/lua2dox/lua2dox_lua \ No newline at end of file diff --git a/Master/bin/amd64-kfreebsd/lua2dox_filter b/Master/bin/amd64-kfreebsd/lua2dox_filter new file mode 120000 index 00000000000..813f7749250 --- /dev/null +++ b/Master/bin/amd64-kfreebsd/lua2dox_filter @@ -0,0 +1 @@ +lua2dox_lua \ No newline at end of file diff --git a/Master/bin/amd64-kfreebsd/lua2dox_lua b/Master/bin/amd64-kfreebsd/lua2dox_lua new file mode 120000 index 00000000000..3dcc4b61c72 --- /dev/null +++ b/Master/bin/amd64-kfreebsd/lua2dox_lua @@ -0,0 +1 @@ +../../texmf-dist/scripts/lua2dox/lua2dox_lua \ No newline at end of file diff --git a/Master/bin/armel-linux/lua2dox_filter b/Master/bin/armel-linux/lua2dox_filter new file mode 120000 index 00000000000..813f7749250 --- /dev/null +++ b/Master/bin/armel-linux/lua2dox_filter @@ -0,0 +1 @@ +lua2dox_lua \ No newline at end of file diff --git a/Master/bin/armel-linux/lua2dox_lua b/Master/bin/armel-linux/lua2dox_lua new file mode 120000 index 00000000000..3dcc4b61c72 --- /dev/null +++ b/Master/bin/armel-linux/lua2dox_lua @@ -0,0 +1 @@ +../../texmf-dist/scripts/lua2dox/lua2dox_lua \ No newline at end of file diff --git a/Master/bin/i386-cygwin/lua2dox_filter b/Master/bin/i386-cygwin/lua2dox_filter new file mode 120000 index 00000000000..813f7749250 --- /dev/null +++ b/Master/bin/i386-cygwin/lua2dox_filter @@ -0,0 +1 @@ +lua2dox_lua \ No newline at end of file diff --git a/Master/bin/i386-cygwin/lua2dox_lua b/Master/bin/i386-cygwin/lua2dox_lua new file mode 120000 index 00000000000..3dcc4b61c72 --- /dev/null +++ b/Master/bin/i386-cygwin/lua2dox_lua @@ -0,0 +1 @@ +../../texmf-dist/scripts/lua2dox/lua2dox_lua \ No newline at end of file diff --git a/Master/bin/i386-freebsd/lua2dox_filter b/Master/bin/i386-freebsd/lua2dox_filter new file mode 120000 index 00000000000..813f7749250 --- /dev/null +++ b/Master/bin/i386-freebsd/lua2dox_filter @@ -0,0 +1 @@ +lua2dox_lua \ No newline at end of file diff --git a/Master/bin/i386-freebsd/lua2dox_lua b/Master/bin/i386-freebsd/lua2dox_lua new file mode 120000 index 00000000000..3dcc4b61c72 --- /dev/null +++ b/Master/bin/i386-freebsd/lua2dox_lua @@ -0,0 +1 @@ +../../texmf-dist/scripts/lua2dox/lua2dox_lua \ No newline at end of file diff --git a/Master/bin/i386-kfreebsd/lua2dox_filter b/Master/bin/i386-kfreebsd/lua2dox_filter new file mode 120000 index 00000000000..813f7749250 --- /dev/null +++ b/Master/bin/i386-kfreebsd/lua2dox_filter @@ -0,0 +1 @@ +lua2dox_lua \ No newline at end of file diff --git a/Master/bin/i386-kfreebsd/lua2dox_lua b/Master/bin/i386-kfreebsd/lua2dox_lua new file mode 120000 index 00000000000..3dcc4b61c72 --- /dev/null +++ b/Master/bin/i386-kfreebsd/lua2dox_lua @@ -0,0 +1 @@ +../../texmf-dist/scripts/lua2dox/lua2dox_lua \ No newline at end of file diff --git a/Master/bin/i386-linux/lua2dox_filter b/Master/bin/i386-linux/lua2dox_filter new file mode 120000 index 00000000000..813f7749250 --- /dev/null +++ b/Master/bin/i386-linux/lua2dox_filter @@ -0,0 +1 @@ +lua2dox_lua \ No newline at end of file diff --git a/Master/bin/i386-linux/lua2dox_lua b/Master/bin/i386-linux/lua2dox_lua new file mode 120000 index 00000000000..3dcc4b61c72 --- /dev/null +++ b/Master/bin/i386-linux/lua2dox_lua @@ -0,0 +1 @@ +../../texmf-dist/scripts/lua2dox/lua2dox_lua \ No newline at end of file diff --git a/Master/bin/i386-solaris/lua2dox_filter b/Master/bin/i386-solaris/lua2dox_filter new file mode 120000 index 00000000000..813f7749250 --- /dev/null +++ b/Master/bin/i386-solaris/lua2dox_filter @@ -0,0 +1 @@ +lua2dox_lua \ No newline at end of file diff --git a/Master/bin/i386-solaris/lua2dox_lua b/Master/bin/i386-solaris/lua2dox_lua new file mode 120000 index 00000000000..3dcc4b61c72 --- /dev/null +++ b/Master/bin/i386-solaris/lua2dox_lua @@ -0,0 +1 @@ +../../texmf-dist/scripts/lua2dox/lua2dox_lua \ No newline at end of file diff --git a/Master/bin/mipsel-linux/lua2dox_filter b/Master/bin/mipsel-linux/lua2dox_filter new file mode 120000 index 00000000000..813f7749250 --- /dev/null +++ b/Master/bin/mipsel-linux/lua2dox_filter @@ -0,0 +1 @@ +lua2dox_lua \ No newline at end of file diff --git a/Master/bin/mipsel-linux/lua2dox_lua b/Master/bin/mipsel-linux/lua2dox_lua new file mode 120000 index 00000000000..3dcc4b61c72 --- /dev/null +++ b/Master/bin/mipsel-linux/lua2dox_lua @@ -0,0 +1 @@ +../../texmf-dist/scripts/lua2dox/lua2dox_lua \ No newline at end of file diff --git a/Master/bin/powerpc-aix/lua2dox_filter b/Master/bin/powerpc-aix/lua2dox_filter new file mode 120000 index 00000000000..813f7749250 --- /dev/null +++ b/Master/bin/powerpc-aix/lua2dox_filter @@ -0,0 +1 @@ +lua2dox_lua \ No newline at end of file diff --git a/Master/bin/powerpc-aix/lua2dox_lua b/Master/bin/powerpc-aix/lua2dox_lua new file mode 120000 index 00000000000..3dcc4b61c72 --- /dev/null +++ b/Master/bin/powerpc-aix/lua2dox_lua @@ -0,0 +1 @@ +../../texmf-dist/scripts/lua2dox/lua2dox_lua \ No newline at end of file diff --git a/Master/bin/powerpc-linux/lua2dox_filter b/Master/bin/powerpc-linux/lua2dox_filter new file mode 120000 index 00000000000..813f7749250 --- /dev/null +++ b/Master/bin/powerpc-linux/lua2dox_filter @@ -0,0 +1 @@ +lua2dox_lua \ No newline at end of file diff --git a/Master/bin/powerpc-linux/lua2dox_lua b/Master/bin/powerpc-linux/lua2dox_lua new file mode 120000 index 00000000000..3dcc4b61c72 --- /dev/null +++ b/Master/bin/powerpc-linux/lua2dox_lua @@ -0,0 +1 @@ +../../texmf-dist/scripts/lua2dox/lua2dox_lua \ No newline at end of file diff --git a/Master/bin/sparc-solaris/lua2dox_filter b/Master/bin/sparc-solaris/lua2dox_filter new file mode 120000 index 00000000000..813f7749250 --- /dev/null +++ b/Master/bin/sparc-solaris/lua2dox_filter @@ -0,0 +1 @@ +lua2dox_lua \ No newline at end of file diff --git a/Master/bin/sparc-solaris/lua2dox_lua b/Master/bin/sparc-solaris/lua2dox_lua new file mode 120000 index 00000000000..3dcc4b61c72 --- /dev/null +++ b/Master/bin/sparc-solaris/lua2dox_lua @@ -0,0 +1 @@ +../../texmf-dist/scripts/lua2dox/lua2dox_lua \ No newline at end of file diff --git a/Master/bin/universal-darwin/lua2dox_filter b/Master/bin/universal-darwin/lua2dox_filter new file mode 120000 index 00000000000..813f7749250 --- /dev/null +++ b/Master/bin/universal-darwin/lua2dox_filter @@ -0,0 +1 @@ +lua2dox_lua \ No newline at end of file diff --git a/Master/bin/universal-darwin/lua2dox_lua b/Master/bin/universal-darwin/lua2dox_lua new file mode 120000 index 00000000000..3dcc4b61c72 --- /dev/null +++ b/Master/bin/universal-darwin/lua2dox_lua @@ -0,0 +1 @@ +../../texmf-dist/scripts/lua2dox/lua2dox_lua \ No newline at end of file diff --git a/Master/bin/x86_64-darwin/lua2dox_filter b/Master/bin/x86_64-darwin/lua2dox_filter new file mode 120000 index 00000000000..813f7749250 --- /dev/null +++ b/Master/bin/x86_64-darwin/lua2dox_filter @@ -0,0 +1 @@ +lua2dox_lua \ No newline at end of file diff --git a/Master/bin/x86_64-darwin/lua2dox_lua b/Master/bin/x86_64-darwin/lua2dox_lua new file mode 120000 index 00000000000..3dcc4b61c72 --- /dev/null +++ b/Master/bin/x86_64-darwin/lua2dox_lua @@ -0,0 +1 @@ +../../texmf-dist/scripts/lua2dox/lua2dox_lua \ No newline at end of file diff --git a/Master/bin/x86_64-linux/lua2dox_filter b/Master/bin/x86_64-linux/lua2dox_filter new file mode 120000 index 00000000000..813f7749250 --- /dev/null +++ b/Master/bin/x86_64-linux/lua2dox_filter @@ -0,0 +1 @@ +lua2dox_lua \ No newline at end of file diff --git a/Master/bin/x86_64-linux/lua2dox_lua b/Master/bin/x86_64-linux/lua2dox_lua new file mode 120000 index 00000000000..3dcc4b61c72 --- /dev/null +++ b/Master/bin/x86_64-linux/lua2dox_lua @@ -0,0 +1 @@ +../../texmf-dist/scripts/lua2dox/lua2dox_lua \ No newline at end of file diff --git a/Master/bin/x86_64-solaris/lua2dox_filter b/Master/bin/x86_64-solaris/lua2dox_filter new file mode 120000 index 00000000000..813f7749250 --- /dev/null +++ b/Master/bin/x86_64-solaris/lua2dox_filter @@ -0,0 +1 @@ +lua2dox_lua \ No newline at end of file diff --git a/Master/bin/x86_64-solaris/lua2dox_lua b/Master/bin/x86_64-solaris/lua2dox_lua new file mode 120000 index 00000000000..3dcc4b61c72 --- /dev/null +++ b/Master/bin/x86_64-solaris/lua2dox_lua @@ -0,0 +1 @@ +../../texmf-dist/scripts/lua2dox/lua2dox_lua \ No newline at end of file diff --git a/Master/texmf-dist/doc/support/lua2dox/Doxyfile b/Master/texmf-dist/doc/support/lua2dox/Doxyfile new file mode 100644 index 00000000000..dd9865d6497 --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/Doxyfile @@ -0,0 +1,1422 @@ +# Doxyfile 1.5.6 + +# This file describes the settings to be used by the documentation system +# doxygen (www.doxygen.org) for a project +# +# All text after a hash (#) is considered a comment and will be ignored +# The format is: +# TAG = value [value, ...] +# For lists items can also be appended using: +# TAG += value [value, ...] +# Values that contain spaces should be placed between quotes (" ") + +#--------------------------------------------------------------------------- +# Project related configuration options +#--------------------------------------------------------------------------- + +# This tag specifies the encoding used for all characters in the config file +# that follow. The default is UTF-8 which is also the encoding used for all +# text before the first occurrence of this tag. Doxygen uses libiconv (or the +# iconv built into libc) for the transcoding. See +# http://www.gnu.org/software/libiconv for the list of possible encodings. + +DOXYFILE_ENCODING = UTF-8 + +# The PROJECT_NAME tag is a single word (or a sequence of words surrounded +# by quotes) that should identify the project. + +PROJECT_NAME = "Lua2dox.lua" + +# The PROJECT_NUMBER tag can be used to enter a project or revision number. +# This could be handy for archiving the generated documentation or +# if some version control system is used. + +PROJECT_NUMBER = "0.1 20120704" + +# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) +# base path where the generated documentation will be put. +# If a relative path is entered, it will be relative to the location +# where doxygen was started. If left blank the current directory will be used. + +OUTPUT_DIRECTORY = docs + +# If the CREATE_SUBDIRS tag is set to YES, then doxygen will create +# 4096 sub-directories (in 2 levels) under the output directory of each output +# format and will distribute the generated files over these directories. +# Enabling this option can be useful when feeding doxygen a huge amount of +# source files, where putting all generated files in the same directory would +# otherwise cause performance problems for the file system. + +CREATE_SUBDIRS = NO + +# The OUTPUT_LANGUAGE tag is used to specify the language in which all +# documentation generated by doxygen is written. Doxygen will use this +# information to generate all constant output in the proper language. +# The default language is English, other supported languages are: +# Afrikaans, Arabic, Brazilian, Catalan, Chinese, Chinese-Traditional, +# Croatian, Czech, Danish, Dutch, Farsi, Finnish, French, German, Greek, +# Hungarian, Italian, Japanese, Japanese-en (Japanese with English messages), +# Korean, Korean-en, Lithuanian, Norwegian, Macedonian, Persian, Polish, +# Portuguese, Romanian, Russian, Serbian, Slovak, Slovene, Spanish, Swedish, +# and Ukrainian. + +OUTPUT_LANGUAGE = English + +# If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will +# include brief member descriptions after the members that are listed in +# the file and class documentation (similar to JavaDoc). +# Set to NO to disable this. + +BRIEF_MEMBER_DESC = YES + +# If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend +# the brief description of a member or function before the detailed description. +# Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the +# brief descriptions will be completely suppressed. + +REPEAT_BRIEF = YES + +# This tag implements a quasi-intelligent brief description abbreviator +# that is used to form the text in various listings. Each string +# in this list, if found as the leading text of the brief description, will be +# stripped from the text and the result after processing the whole list, is +# used as the annotated text. Otherwise, the brief description is used as-is. +# If left blank, the following values are used ("$name" is automatically +# replaced with the name of the entity): "The $name class" "The $name widget" +# "The $name file" "is" "provides" "specifies" "contains" +# "represents" "a" "an" "the" + +ABBREVIATE_BRIEF = + +# If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then +# Doxygen will generate a detailed section even if there is only a brief +# description. + +ALWAYS_DETAILED_SEC = NO + +# If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all +# inherited members of a class in the documentation of that class as if those +# members were ordinary class members. Constructors, destructors and assignment +# operators of the base classes will not be shown. + +INLINE_INHERITED_MEMB = NO + +# If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full +# path before files name in the file list and in the header files. If set +# to NO the shortest path that makes the file name unique will be used. + +FULL_PATH_NAMES = YES + +# If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag +# can be used to strip a user-defined part of the path. Stripping is +# only done if one of the specified strings matches the left-hand part of +# the path. The tag can be used to show relative paths in the file list. +# If left blank the directory from which doxygen is run is used as the +# path to strip. + +STRIP_FROM_PATH = + +# The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of +# the path mentioned in the documentation of a class, which tells +# the reader which header file to include in order to use a class. +# If left blank only the name of the header file containing the class +# definition is used. Otherwise one should specify the include paths that +# are normally passed to the compiler using the -I flag. + +STRIP_FROM_INC_PATH = + +# If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter +# (but less readable) file names. This can be useful is your file systems +# doesn't support long names like on DOS, Mac, or CD-ROM. + +SHORT_NAMES = NO + +# If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen +# will interpret the first line (until the first dot) of a JavaDoc-style +# comment as the brief description. If set to NO, the JavaDoc +# comments will behave just like regular Qt-style comments +# (thus requiring an explicit @brief command for a brief description.) + +JAVADOC_AUTOBRIEF = NO + +# If the QT_AUTOBRIEF tag is set to YES then Doxygen will +# interpret the first line (until the first dot) of a Qt-style +# comment as the brief description. If set to NO, the comments +# will behave just like regular Qt-style comments (thus requiring +# an explicit \brief command for a brief description.) + +QT_AUTOBRIEF = NO + +# The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen +# treat a multi-line C++ special comment block (i.e. a block of //! or /// +# comments) as a brief description. This used to be the default behaviour. +# The new default is to treat a multi-line C++ comment block as a detailed +# description. Set this tag to YES if you prefer the old behaviour instead. + +MULTILINE_CPP_IS_BRIEF = NO + +# If the DETAILS_AT_TOP tag is set to YES then Doxygen +# will output the detailed description near the top, like JavaDoc. +# If set to NO, the detailed description appears after the member +# documentation. + +DETAILS_AT_TOP = NO + +# If the INHERIT_DOCS tag is set to YES (the default) then an undocumented +# member inherits the documentation from any documented member that it +# re-implements. + +INHERIT_DOCS = YES + +# If the SEPARATE_MEMBER_PAGES tag is set to YES, then doxygen will produce +# a new page for each member. If set to NO, the documentation of a member will +# be part of the file/class/namespace that contains it. + +SEPARATE_MEMBER_PAGES = NO + +# The TAB_SIZE tag can be used to set the number of spaces in a tab. +# Doxygen uses this value to replace tabs by spaces in code fragments. + +TAB_SIZE = 2 + +# This tag can be used to specify a number of aliases that acts +# as commands in the documentation. An alias has the form "name=value". +# For example adding "sideeffect=\par Side Effects:\n" will allow you to +# put the command \sideeffect (or @sideeffect) in the documentation, which +# will result in a user-defined paragraph with heading "Side Effects:". +# You can put \n's in the value part of an alias to insert newlines. + +ALIASES = + +# Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C +# sources only. Doxygen will then generate output that is more tailored for C. +# For instance, some of the names that are used will be different. The list +# of all members will be omitted, etc. + +OPTIMIZE_OUTPUT_FOR_C = NO + +# Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java +# sources only. Doxygen will then generate output that is more tailored for +# Java. For instance, namespaces will be presented as packages, qualified +# scopes will look different, etc. + +OPTIMIZE_OUTPUT_JAVA = NO + +# Set the OPTIMIZE_FOR_FORTRAN tag to YES if your project consists of Fortran +# sources only. Doxygen will then generate output that is more tailored for +# Fortran. + +OPTIMIZE_FOR_FORTRAN = NO + +# Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL +# sources. Doxygen will then generate output that is tailored for +# VHDL. + +OPTIMIZE_OUTPUT_VHDL = NO + +# If you use STL classes (i.e. std::string, std::vector, etc.) but do not want +# to include (a tag file for) the STL sources as input, then you should +# set this tag to YES in order to let doxygen match functions declarations and +# definitions whose arguments contain STL classes (e.g. func(std::string); v.s. +# func(std::string) {}). This also make the inheritance and collaboration +# diagrams that involve STL classes more complete and accurate. + +BUILTIN_STL_SUPPORT = NO + +# If you use Microsoft's C++/CLI language, you should set this option to YES to +# enable parsing support. + +CPP_CLI_SUPPORT = NO + +# Set the SIP_SUPPORT tag to YES if your project consists of sip sources only. +# Doxygen will parse them like normal C++ but will assume all classes use public +# instead of private inheritance when no explicit protection keyword is present. + +SIP_SUPPORT = NO + +# For Microsoft's IDL there are propget and propput attributes to indicate getter +# and setter methods for a property. Setting this option to YES (the default) +# will make doxygen to replace the get and set methods by a property in the +# documentation. This will only work if the methods are indeed getting or +# setting a simple type. If this is not the case, or you want to show the +# methods anyway, you should set this option to NO. + +IDL_PROPERTY_SUPPORT = YES + +# If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC +# tag is set to YES, then doxygen will reuse the documentation of the first +# member in the group (if any) for the other members of the group. By default +# all members of a group must be documented explicitly. + +DISTRIBUTE_GROUP_DOC = NO + +# Set the SUBGROUPING tag to YES (the default) to allow class member groups of +# the same type (for instance a group of public functions) to be put as a +# subgroup of that type (e.g. under the Public Functions section). Set it to +# NO to prevent subgrouping. Alternatively, this can be done per class using +# the \nosubgrouping command. + +SUBGROUPING = YES + +# When TYPEDEF_HIDES_STRUCT is enabled, a typedef of a struct, union, or enum +# is documented as struct, union, or enum with the name of the typedef. So +# typedef struct TypeS {} TypeT, will appear in the documentation as a struct +# with name TypeT. When disabled the typedef will appear as a member of a file, +# namespace, or class. And the struct will be named TypeS. This can typically +# be useful for C code in case the coding convention dictates that all compound +# types are typedef'ed and only the typedef is referenced, never the tag name. + +TYPEDEF_HIDES_STRUCT = NO + +#--------------------------------------------------------------------------- +# Build related configuration options +#--------------------------------------------------------------------------- + +# If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in +# documentation are documented, even if no documentation was available. +# Private class members and static file members will be hidden unless +# the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES + +#EXTRACT_ALL = NO +EXTRACT_ALL = yes + +# If the EXTRACT_PRIVATE tag is set to YES all private members of a class +# will be included in the documentation. + +EXTRACT_PRIVATE = NO + +# If the EXTRACT_STATIC tag is set to YES all static members of a file +# will be included in the documentation. + +EXTRACT_STATIC = NO + +# If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs) +# defined locally in source files will be included in the documentation. +# If set to NO only classes defined in header files are included. + +EXTRACT_LOCAL_CLASSES = YES + +# This flag is only useful for Objective-C code. When set to YES local +# methods, which are defined in the implementation section but not in +# the interface are included in the documentation. +# If set to NO (the default) only methods in the interface are included. + +EXTRACT_LOCAL_METHODS = NO + +# If this flag is set to YES, the members of anonymous namespaces will be +# extracted and appear in the documentation as a namespace called +# 'anonymous_namespace{file}', where file will be replaced with the base +# name of the file that contains the anonymous namespace. By default +# anonymous namespace are hidden. + +EXTRACT_ANON_NSPACES = NO + +# If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all +# undocumented members of documented classes, files or namespaces. +# If set to NO (the default) these members will be included in the +# various overviews, but no documentation section is generated. +# This option has no effect if EXTRACT_ALL is enabled. + +HIDE_UNDOC_MEMBERS = NO + +# If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all +# undocumented classes that are normally visible in the class hierarchy. +# If set to NO (the default) these classes will be included in the various +# overviews. This option has no effect if EXTRACT_ALL is enabled. + +HIDE_UNDOC_CLASSES = NO + +# If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all +# friend (class|struct|union) declarations. +# If set to NO (the default) these declarations will be included in the +# documentation. + +HIDE_FRIEND_COMPOUNDS = NO + +# If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any +# documentation blocks found inside the body of a function. +# If set to NO (the default) these blocks will be appended to the +# function's detailed documentation block. + +HIDE_IN_BODY_DOCS = NO + +# The INTERNAL_DOCS tag determines if documentation +# that is typed after a \internal command is included. If the tag is set +# to NO (the default) then the documentation will be excluded. +# Set it to YES to include the internal documentation. + +INTERNAL_DOCS = NO + +# If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate +# file names in lower-case letters. If set to YES upper-case letters are also +# allowed. This is useful if you have classes or files whose names only differ +# in case and if your file system supports case sensitive file names. Windows +# and Mac users are advised to set this option to NO. + +CASE_SENSE_NAMES = YES + +# If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen +# will show members with their full class and namespace scopes in the +# documentation. If set to YES the scope will be hidden. + +HIDE_SCOPE_NAMES = NO + +# If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen +# will put a list of the files that are included by a file in the documentation +# of that file. + +SHOW_INCLUDE_FILES = YES + +# If the INLINE_INFO tag is set to YES (the default) then a tag [inline] +# is inserted in the documentation for inline members. + +INLINE_INFO = YES + +# If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen +# will sort the (detailed) documentation of file and class members +# alphabetically by member name. If set to NO the members will appear in +# declaration order. + +SORT_MEMBER_DOCS = YES + +# If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the +# brief documentation of file, namespace and class members alphabetically +# by member name. If set to NO (the default) the members will appear in +# declaration order. + +#SORT_BRIEF_DOCS = NO +SORT_BRIEF_DOCS = yes + +# If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the +# hierarchy of group names into alphabetical order. If set to NO (the default) +# the group names will appear in their defined order. + +SORT_GROUP_NAMES = NO + +# If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be +# sorted by fully-qualified names, including namespaces. If set to +# NO (the default), the class list will be sorted only by class name, +# not including the namespace part. +# Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES. +# Note: This option applies only to the class list, not to the +# alphabetical list. + +SORT_BY_SCOPE_NAME = NO + +# The GENERATE_TODOLIST tag can be used to enable (YES) or +# disable (NO) the todo list. This list is created by putting \todo +# commands in the documentation. + +GENERATE_TODOLIST = YES + +# The GENERATE_TESTLIST tag can be used to enable (YES) or +# disable (NO) the test list. This list is created by putting \test +# commands in the documentation. + +GENERATE_TESTLIST = YES + +# The GENERATE_BUGLIST tag can be used to enable (YES) or +# disable (NO) the bug list. This list is created by putting \bug +# commands in the documentation. + +GENERATE_BUGLIST = YES + +# The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or +# disable (NO) the deprecated list. This list is created by putting +# \deprecated commands in the documentation. + +GENERATE_DEPRECATEDLIST= YES + +# The ENABLED_SECTIONS tag can be used to enable conditional +# documentation sections, marked by \if sectionname ... \endif. + +ENABLED_SECTIONS = + +# The MAX_INITIALIZER_LINES tag determines the maximum number of lines +# the initial value of a variable or define consists of for it to appear in +# the documentation. If the initializer consists of more lines than specified +# here it will be hidden. Use a value of 0 to hide initializers completely. +# The appearance of the initializer of individual variables and defines in the +# documentation can be controlled using \showinitializer or \hideinitializer +# command in the documentation regardless of this setting. + +MAX_INITIALIZER_LINES = 30 + +# Set the SHOW_USED_FILES tag to NO to disable the list of files generated +# at the bottom of the documentation of classes and structs. If set to YES the +# list will mention the files that were used to generate the documentation. + +SHOW_USED_FILES = YES + +# If the sources in your project are distributed over multiple directories +# then setting the SHOW_DIRECTORIES tag to YES will show the directory hierarchy +# in the documentation. The default is NO. + +SHOW_DIRECTORIES = NO + +# Set the SHOW_FILES tag to NO to disable the generation of the Files page. +# This will remove the Files entry from the Quick Index and from the +# Folder Tree View (if specified). The default is YES. + +SHOW_FILES = YES + +# Set the SHOW_NAMESPACES tag to NO to disable the generation of the +# Namespaces page. This will remove the Namespaces entry from the Quick Index +# and from the Folder Tree View (if specified). The default is YES. + +SHOW_NAMESPACES = YES + +# The FILE_VERSION_FILTER tag can be used to specify a program or script that +# doxygen should invoke to get the current version for each file (typically from +# the version control system). Doxygen will invoke the program by executing (via +# popen()) the command , where is the value of +# the FILE_VERSION_FILTER tag, and is the name of an input file +# provided by doxygen. Whatever the program writes to standard output +# is used as the file version. See the manual for examples. + +FILE_VERSION_FILTER = + +#--------------------------------------------------------------------------- +# configuration options related to warning and progress messages +#--------------------------------------------------------------------------- + +# The QUIET tag can be used to turn on/off the messages that are generated +# by doxygen. Possible values are YES and NO. If left blank NO is used. + +QUIET = NO + +# The WARNINGS tag can be used to turn on/off the warning messages that are +# generated by doxygen. Possible values are YES and NO. If left blank +# NO is used. + +WARNINGS = YES + +# If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings +# for undocumented members. If EXTRACT_ALL is set to YES then this flag will +# automatically be disabled. + +WARN_IF_UNDOCUMENTED = YES + +# If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for +# potential errors in the documentation, such as not documenting some +# parameters in a documented function, or documenting parameters that +# don't exist or using markup commands wrongly. + +WARN_IF_DOC_ERROR = YES + +# This WARN_NO_PARAMDOC option can be abled to get warnings for +# functions that are documented, but have no documentation for their parameters +# or return value. If set to NO (the default) doxygen will only warn about +# wrong or incomplete parameter documentation, but not about the absence of +# documentation. + +WARN_NO_PARAMDOC = NO + +# The WARN_FORMAT tag determines the format of the warning messages that +# doxygen can produce. The string should contain the $file, $line, and $text +# tags, which will be replaced by the file and line number from which the +# warning originated and the warning text. Optionally the format may contain +# $version, which will be replaced by the version of the file (if it could +# be obtained via FILE_VERSION_FILTER) + +WARN_FORMAT = "$file:$line: $text" + +# The WARN_LOGFILE tag can be used to specify a file to which warning +# and error messages should be written. If left blank the output is written +# to stderr. + +WARN_LOGFILE = + +#--------------------------------------------------------------------------- +# configuration options related to the input files +#--------------------------------------------------------------------------- + +# The INPUT tag can be used to specify the files and/or directories that contain +# documented source files. You may enter file names like "myfile.cpp" or +# directories like "/usr/src/myproject". Separate the files or directories +# with spaces. + +INPUT = + +# This tag can be used to specify the character encoding of the source files +# that doxygen parses. Internally doxygen uses the UTF-8 encoding, which is +# also the default input encoding. Doxygen uses libiconv (or the iconv built +# into libc) for the transcoding. See http://www.gnu.org/software/libiconv for +# the list of possible encodings. + +INPUT_ENCODING = UTF-8 + +# If the value of the INPUT tag contains directories, you can use the +# FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp +# and *.h) to filter out the source-files in the directories. If left +# blank the following patterns are tested: +# *.c *.cc *.cxx *.cpp *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx +# *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm *.py *.f90 + +FILE_PATTERNS = *.lua + +# The RECURSIVE tag can be used to turn specify whether or not subdirectories +# should be searched for input files as well. Possible values are YES and NO. +# If left blank NO is used. + +RECURSIVE = NO + +# The EXCLUDE tag can be used to specify files and/or directories that should +# excluded from the INPUT source files. This way you can easily exclude a +# subdirectory from a directory tree whose root is specified with the INPUT tag. + +EXCLUDE = + +# The EXCLUDE_SYMLINKS tag can be used select whether or not files or +# directories that are symbolic links (a Unix filesystem feature) are excluded +# from the input. + +EXCLUDE_SYMLINKS = NO + +# If the value of the INPUT tag contains directories, you can use the +# EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude +# certain files from those directories. Note that the wildcards are matched +# against the file with absolute path, so to exclude all test directories +# for example use the pattern */test/* + +EXCLUDE_PATTERNS = + +# The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names +# (namespaces, classes, functions, etc.) that should be excluded from the +# output. The symbol name can be a fully qualified name, a word, or if the +# wildcard * is used, a substring. Examples: ANamespace, AClass, +# AClass::ANamespace, ANamespace::*Test + +EXCLUDE_SYMBOLS = + +# The EXAMPLE_PATH tag can be used to specify one or more files or +# directories that contain example code fragments that are included (see +# the \include command). + +EXAMPLE_PATH = + +# If the value of the EXAMPLE_PATH tag contains directories, you can use the +# EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp +# and *.h) to filter out the source-files in the directories. If left +# blank all files are included. + +EXAMPLE_PATTERNS = + +# If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be +# searched for input files to be used with the \include or \dontinclude +# commands irrespective of the value of the RECURSIVE tag. +# Possible values are YES and NO. If left blank NO is used. + +EXAMPLE_RECURSIVE = NO + +# The IMAGE_PATH tag can be used to specify one or more files or +# directories that contain image that are included in the documentation (see +# the \image command). + +IMAGE_PATH = + +# The INPUT_FILTER tag can be used to specify a program that doxygen should +# invoke to filter for each input file. Doxygen will invoke the filter program +# by executing (via popen()) the command , where +# is the value of the INPUT_FILTER tag, and is the name of an +# input file. Doxygen will then use the output that the filter program writes +# to standard output. If FILTER_PATTERNS is specified, this tag will be +# ignored. + +INPUT_FILTER = + +# The FILTER_PATTERNS tag can be used to specify filters on a per file pattern +# basis. Doxygen will compare the file name with each pattern and apply the +# filter if there is a match. The filters are a list of the form: +# pattern=filter (like *.cpp=my_cpp_filter). See INPUT_FILTER for further +# info on how filters are used. If FILTER_PATTERNS is empty, INPUT_FILTER +# is applied to all files. + +FILTER_PATTERNS = *.lua=lua2dox_filter + +# If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using +# INPUT_FILTER) will be used to filter the input files when producing source +# files to browse (i.e. when SOURCE_BROWSER is set to YES). + +FILTER_SOURCE_FILES = NO + +#--------------------------------------------------------------------------- +# configuration options related to source browsing +#--------------------------------------------------------------------------- + +# If the SOURCE_BROWSER tag is set to YES then a list of source files will +# be generated. Documented entities will be cross-referenced with these sources. +# Note: To get rid of all source code in the generated output, make sure also +# VERBATIM_HEADERS is set to NO. + +#SOURCE_BROWSER = NO +SOURCE_BROWSER = yes + +# Setting the INLINE_SOURCES tag to YES will include the body +# of functions and classes directly in the documentation. + +INLINE_SOURCES = NO + +# Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct +# doxygen to hide any special comment blocks from generated source code +# fragments. Normal C and C++ comments will always remain visible. + +STRIP_CODE_COMMENTS = YES + +# If the REFERENCED_BY_RELATION tag is set to YES +# then for each documented function all documented +# functions referencing it will be listed. + +REFERENCED_BY_RELATION = NO + +# If the REFERENCES_RELATION tag is set to YES +# then for each documented function all documented entities +# called/used by that function will be listed. + +REFERENCES_RELATION = NO + +# If the REFERENCES_LINK_SOURCE tag is set to YES (the default) +# and SOURCE_BROWSER tag is set to YES, then the hyperlinks from +# functions in REFERENCES_RELATION and REFERENCED_BY_RELATION lists will +# link to the source code. Otherwise they will link to the documentstion. + +REFERENCES_LINK_SOURCE = YES + +# If the USE_HTAGS tag is set to YES then the references to source code +# will point to the HTML generated by the htags(1) tool instead of doxygen +# built-in source browser. The htags tool is part of GNU's global source +# tagging system (see http://www.gnu.org/software/global/global.html). You +# will need version 4.8.6 or higher. + +USE_HTAGS = NO + +# If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen +# will generate a verbatim copy of the header file for each class for +# which an include is specified. Set to NO to disable this. + +VERBATIM_HEADERS = YES + +#--------------------------------------------------------------------------- +# configuration options related to the alphabetical class index +#--------------------------------------------------------------------------- + +# If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index +# of all compounds will be generated. Enable this if the project +# contains a lot of classes, structs, unions or interfaces. + +#ALPHABETICAL_INDEX = NO +ALPHABETICAL_INDEX = yes + +# If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then +# the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns +# in which this list will be split (can be a number in the range [1..20]) + +COLS_IN_ALPHA_INDEX = 5 + +# In case all classes in a project start with a common prefix, all +# classes will be put under the same header in the alphabetical index. +# The IGNORE_PREFIX tag can be used to specify one or more prefixes that +# should be ignored while generating the index headers. + +IGNORE_PREFIX = + +#--------------------------------------------------------------------------- +# configuration options related to the HTML output +#--------------------------------------------------------------------------- + +# If the GENERATE_HTML tag is set to YES (the default) Doxygen will +# generate HTML output. + +GENERATE_HTML = YES + +# The HTML_OUTPUT tag is used to specify where the HTML docs will be put. +# If a relative path is entered the value of OUTPUT_DIRECTORY will be +# put in front of it. If left blank `html' will be used as the default path. + +HTML_OUTPUT = html + +# The HTML_FILE_EXTENSION tag can be used to specify the file extension for +# each generated HTML page (for example: .htm,.php,.asp). If it is left blank +# doxygen will generate files with .html extension. + +HTML_FILE_EXTENSION = .html + +# The HTML_HEADER tag can be used to specify a personal HTML header for +# each generated HTML page. If it is left blank doxygen will generate a +# standard header. + +HTML_HEADER = + +# The HTML_FOOTER tag can be used to specify a personal HTML footer for +# each generated HTML page. If it is left blank doxygen will generate a +# standard footer. + +HTML_FOOTER = + +# The HTML_STYLESHEET tag can be used to specify a user-defined cascading +# style sheet that is used by each HTML page. It can be used to +# fine-tune the look of the HTML output. If the tag is left blank doxygen +# will generate a default style sheet. Note that doxygen will try to copy +# the style sheet file to the HTML output directory, so don't put your own +# stylesheet in the HTML output directory as well, or it will be erased! + +HTML_STYLESHEET = + +# If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes, +# files or namespaces will be aligned in HTML using tables. If set to +# NO a bullet list will be used. + +HTML_ALIGN_MEMBERS = YES + +# If the GENERATE_HTMLHELP tag is set to YES, additional index files +# will be generated that can be used as input for tools like the +# Microsoft HTML help workshop to generate a compiled HTML help file (.chm) +# of the generated HTML documentation. + +GENERATE_HTMLHELP = NO + +# If the GENERATE_DOCSET tag is set to YES, additional index files +# will be generated that can be used as input for Apple's Xcode 3 +# integrated development environment, introduced with OSX 10.5 (Leopard). +# To create a documentation set, doxygen will generate a Makefile in the +# HTML output directory. Running make will produce the docset in that +# directory and running "make install" will install the docset in +# ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find +# it at startup. + +GENERATE_DOCSET = NO + +# When GENERATE_DOCSET tag is set to YES, this tag determines the name of the +# feed. A documentation feed provides an umbrella under which multiple +# documentation sets from a single provider (such as a company or product suite) +# can be grouped. + +DOCSET_FEEDNAME = "Doxygen generated docs" + +# When GENERATE_DOCSET tag is set to YES, this tag specifies a string that +# should uniquely identify the documentation set bundle. This should be a +# reverse domain-name style string, e.g. com.mycompany.MyDocSet. Doxygen +# will append .docset to the name. + +DOCSET_BUNDLE_ID = org.doxygen.Project + +# If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML +# documentation will contain sections that can be hidden and shown after the +# page has loaded. For this to work a browser that supports +# JavaScript and DHTML is required (for instance Mozilla 1.0+, Firefox +# Netscape 6.0+, Internet explorer 5.0+, Konqueror, or Safari). + +HTML_DYNAMIC_SECTIONS = NO + +# If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can +# be used to specify the file name of the resulting .chm file. You +# can add a path in front of the file if the result should not be +# written to the html output directory. + +CHM_FILE = + +# If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can +# be used to specify the location (absolute path including file name) of +# the HTML help compiler (hhc.exe). If non-empty doxygen will try to run +# the HTML help compiler on the generated index.hhp. + +HHC_LOCATION = + +# If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag +# controls if a separate .chi index file is generated (YES) or that +# it should be included in the master .chm file (NO). + +GENERATE_CHI = NO + +# If the GENERATE_HTMLHELP tag is set to YES, the CHM_INDEX_ENCODING +# is used to encode HtmlHelp index (hhk), content (hhc) and project file +# content. + +CHM_INDEX_ENCODING = + +# If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag +# controls whether a binary table of contents is generated (YES) or a +# normal table of contents (NO) in the .chm file. + +BINARY_TOC = NO + +# The TOC_EXPAND flag can be set to YES to add extra items for group members +# to the contents of the HTML help documentation and to the tree view. + +TOC_EXPAND = NO + +# The DISABLE_INDEX tag can be used to turn on/off the condensed index at +# top of each HTML page. The value NO (the default) enables the index and +# the value YES disables it. + +DISABLE_INDEX = NO + +# This tag can be used to set the number of enum values (range [1..20]) +# that doxygen will group on one line in the generated HTML documentation. + +ENUM_VALUES_PER_LINE = 4 + +# The GENERATE_TREEVIEW tag is used to specify whether a tree-like index +# structure should be generated to display hierarchical information. +# If the tag value is set to FRAME, a side panel will be generated +# containing a tree-like index structure (just like the one that +# is generated for HTML Help). For this to work a browser that supports +# JavaScript, DHTML, CSS and frames is required (for instance Mozilla 1.0+, +# Netscape 6.0+, Internet explorer 5.0+, or Konqueror). Windows users are +# probably better off using the HTML help feature. Other possible values +# for this tag are: HIERARCHIES, which will generate the Groups, Directories, +# and Class Hiererachy pages using a tree view instead of an ordered list; +# ALL, which combines the behavior of FRAME and HIERARCHIES; and NONE, which +# disables this behavior completely. For backwards compatibility with previous +# releases of Doxygen, the values YES and NO are equivalent to FRAME and NONE +# respectively. + +GENERATE_TREEVIEW = NONE + +# If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be +# used to set the initial width (in pixels) of the frame in which the tree +# is shown. + +TREEVIEW_WIDTH = 250 + +# Use this tag to change the font size of Latex formulas included +# as images in the HTML documentation. The default is 10. Note that +# when you change the font size after a successful doxygen run you need +# to manually remove any form_*.png images from the HTML output directory +# to force them to be regenerated. + +FORMULA_FONTSIZE = 10 + +#--------------------------------------------------------------------------- +# configuration options related to the LaTeX output +#--------------------------------------------------------------------------- + +# If the GENERATE_LATEX tag is set to YES (the default) Doxygen will +# generate Latex output. + +#GENERATE_LATEX = YES +GENERATE_LATEX = no + +# The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put. +# If a relative path is entered the value of OUTPUT_DIRECTORY will be +# put in front of it. If left blank `latex' will be used as the default path. + +LATEX_OUTPUT = latex + +# The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be +# invoked. If left blank `latex' will be used as the default command name. + +LATEX_CMD_NAME = latex + +# The MAKEINDEX_CMD_NAME tag can be used to specify the command name to +# generate index for LaTeX. If left blank `makeindex' will be used as the +# default command name. + +MAKEINDEX_CMD_NAME = makeindex + +# If the COMPACT_LATEX tag is set to YES Doxygen generates more compact +# LaTeX documents. This may be useful for small projects and may help to +# save some trees in general. + +COMPACT_LATEX = NO + +# The PAPER_TYPE tag can be used to set the paper type that is used +# by the printer. Possible values are: a4, a4wide, letter, legal and +# executive. If left blank a4wide will be used. + +PAPER_TYPE = a4wide + +# The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX +# packages that should be included in the LaTeX output. + +EXTRA_PACKAGES = + +# The LATEX_HEADER tag can be used to specify a personal LaTeX header for +# the generated latex document. The header should contain everything until +# the first chapter. If it is left blank doxygen will generate a +# standard header. Notice: only use this tag if you know what you are doing! + +LATEX_HEADER = + +# If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated +# is prepared for conversion to pdf (using ps2pdf). The pdf file will +# contain links (just like the HTML output) instead of page references +# This makes the output suitable for online browsing using a pdf viewer. + +PDF_HYPERLINKS = YES + +# If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of +# plain latex in the generated Makefile. Set this option to YES to get a +# higher quality PDF documentation. + +USE_PDFLATEX = YES + +# If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode. +# command to the generated LaTeX files. This will instruct LaTeX to keep +# running if errors occur, instead of asking the user for help. +# This option is also used when generating formulas in HTML. + +LATEX_BATCHMODE = NO + +# If LATEX_HIDE_INDICES is set to YES then doxygen will not +# include the index chapters (such as File Index, Compound Index, etc.) +# in the output. + +LATEX_HIDE_INDICES = NO + +#--------------------------------------------------------------------------- +# configuration options related to the RTF output +#--------------------------------------------------------------------------- + +# If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output +# The RTF output is optimized for Word 97 and may not look very pretty with +# other RTF readers or editors. + +GENERATE_RTF = NO + +# The RTF_OUTPUT tag is used to specify where the RTF docs will be put. +# If a relative path is entered the value of OUTPUT_DIRECTORY will be +# put in front of it. If left blank `rtf' will be used as the default path. + +RTF_OUTPUT = rtf + +# If the COMPACT_RTF tag is set to YES Doxygen generates more compact +# RTF documents. This may be useful for small projects and may help to +# save some trees in general. + +COMPACT_RTF = NO + +# If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated +# will contain hyperlink fields. The RTF file will +# contain links (just like the HTML output) instead of page references. +# This makes the output suitable for online browsing using WORD or other +# programs which support those fields. +# Note: wordpad (write) and others do not support links. + +RTF_HYPERLINKS = NO + +# Load stylesheet definitions from file. Syntax is similar to doxygen's +# config file, i.e. a series of assignments. You only have to provide +# replacements, missing definitions are set to their default value. + +RTF_STYLESHEET_FILE = + +# Set optional variables used in the generation of an rtf document. +# Syntax is similar to doxygen's config file. + +RTF_EXTENSIONS_FILE = + +#--------------------------------------------------------------------------- +# configuration options related to the man page output +#--------------------------------------------------------------------------- + +# If the GENERATE_MAN tag is set to YES (the default) Doxygen will +# generate man pages + +GENERATE_MAN = NO + +# The MAN_OUTPUT tag is used to specify where the man pages will be put. +# If a relative path is entered the value of OUTPUT_DIRECTORY will be +# put in front of it. If left blank `man' will be used as the default path. + +MAN_OUTPUT = man + +# The MAN_EXTENSION tag determines the extension that is added to +# the generated man pages (default is the subroutine's section .3) + +MAN_EXTENSION = .3 + +# If the MAN_LINKS tag is set to YES and Doxygen generates man output, +# then it will generate one additional man file for each entity +# documented in the real man page(s). These additional files +# only source the real man page, but without them the man command +# would be unable to find the correct page. The default is NO. + +MAN_LINKS = NO + +#--------------------------------------------------------------------------- +# configuration options related to the XML output +#--------------------------------------------------------------------------- + +# If the GENERATE_XML tag is set to YES Doxygen will +# generate an XML file that captures the structure of +# the code including all documentation. + +GENERATE_XML = NO + +# The XML_OUTPUT tag is used to specify where the XML pages will be put. +# If a relative path is entered the value of OUTPUT_DIRECTORY will be +# put in front of it. If left blank `xml' will be used as the default path. + +XML_OUTPUT = xml + +# The XML_SCHEMA tag can be used to specify an XML schema, +# which can be used by a validating XML parser to check the +# syntax of the XML files. + +XML_SCHEMA = + +# The XML_DTD tag can be used to specify an XML DTD, +# which can be used by a validating XML parser to check the +# syntax of the XML files. + +XML_DTD = + +# If the XML_PROGRAMLISTING tag is set to YES Doxygen will +# dump the program listings (including syntax highlighting +# and cross-referencing information) to the XML output. Note that +# enabling this will significantly increase the size of the XML output. + +XML_PROGRAMLISTING = YES + +#--------------------------------------------------------------------------- +# configuration options for the AutoGen Definitions output +#--------------------------------------------------------------------------- + +# If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will +# generate an AutoGen Definitions (see autogen.sf.net) file +# that captures the structure of the code including all +# documentation. Note that this feature is still experimental +# and incomplete at the moment. + +GENERATE_AUTOGEN_DEF = NO + +#--------------------------------------------------------------------------- +# configuration options related to the Perl module output +#--------------------------------------------------------------------------- + +# If the GENERATE_PERLMOD tag is set to YES Doxygen will +# generate a Perl module file that captures the structure of +# the code including all documentation. Note that this +# feature is still experimental and incomplete at the +# moment. + +GENERATE_PERLMOD = NO + +# If the PERLMOD_LATEX tag is set to YES Doxygen will generate +# the necessary Makefile rules, Perl scripts and LaTeX code to be able +# to generate PDF and DVI output from the Perl module output. + +PERLMOD_LATEX = NO + +# If the PERLMOD_PRETTY tag is set to YES the Perl module output will be +# nicely formatted so it can be parsed by a human reader. This is useful +# if you want to understand what is going on. On the other hand, if this +# tag is set to NO the size of the Perl module output will be much smaller +# and Perl will parse it just the same. + +PERLMOD_PRETTY = YES + +# The names of the make variables in the generated doxyrules.make file +# are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX. +# This is useful so different doxyrules.make files included by the same +# Makefile don't overwrite each other's variables. + +PERLMOD_MAKEVAR_PREFIX = + +#--------------------------------------------------------------------------- +# Configuration options related to the preprocessor +#--------------------------------------------------------------------------- + +# If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will +# evaluate all C-preprocessor directives found in the sources and include +# files. + +ENABLE_PREPROCESSING = YES + +# If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro +# names in the source code. If set to NO (the default) only conditional +# compilation will be performed. Macro expansion can be done in a controlled +# way by setting EXPAND_ONLY_PREDEF to YES. + +MACRO_EXPANSION = NO + +# If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES +# then the macro expansion is limited to the macros specified with the +# PREDEFINED and EXPAND_AS_DEFINED tags. + +EXPAND_ONLY_PREDEF = NO + +# If the SEARCH_INCLUDES tag is set to YES (the default) the includes files +# in the INCLUDE_PATH (see below) will be search if a #include is found. + +SEARCH_INCLUDES = YES + +# The INCLUDE_PATH tag can be used to specify one or more directories that +# contain include files that are not input files but should be processed by +# the preprocessor. + +INCLUDE_PATH = + +# You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard +# patterns (like *.h and *.hpp) to filter out the header-files in the +# directories. If left blank, the patterns specified with FILE_PATTERNS will +# be used. + +INCLUDE_FILE_PATTERNS = + +# The PREDEFINED tag can be used to specify one or more macro names that +# are defined before the preprocessor is started (similar to the -D option of +# gcc). The argument of the tag is a list of macros of the form: name +# or name=definition (no spaces). If the definition and the = are +# omitted =1 is assumed. To prevent a macro definition from being +# undefined via #undef or recursively expanded use the := operator +# instead of the = operator. + +PREDEFINED = + +# If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then +# this tag can be used to specify a list of macro names that should be expanded. +# The macro definition that is found in the sources will be used. +# Use the PREDEFINED tag if you want to use a different macro definition. + +EXPAND_AS_DEFINED = + +# If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then +# doxygen's preprocessor will remove all function-like macros that are alone +# on a line, have an all uppercase name, and do not end with a semicolon. Such +# function macros are typically used for boiler-plate code, and will confuse +# the parser if not removed. + +SKIP_FUNCTION_MACROS = YES + +#--------------------------------------------------------------------------- +# Configuration::additions related to external references +#--------------------------------------------------------------------------- + +# The TAGFILES option can be used to specify one or more tagfiles. +# Optionally an initial location of the external documentation +# can be added for each tagfile. The format of a tag file without +# this location is as follows: +# TAGFILES = file1 file2 ... +# Adding location for the tag files is done as follows: +# TAGFILES = file1=loc1 "file2 = loc2" ... +# where "loc1" and "loc2" can be relative or absolute paths or +# URLs. If a location is present for each tag, the installdox tool +# does not have to be run to correct the links. +# Note that each tag file must have a unique name +# (where the name does NOT include the path) +# If a tag file is not located in the directory in which doxygen +# is run, you must also specify the path to the tagfile here. + +TAGFILES = + +# When a file name is specified after GENERATE_TAGFILE, doxygen will create +# a tag file that is based on the input files it reads. + +GENERATE_TAGFILE = + +# If the ALLEXTERNALS tag is set to YES all external classes will be listed +# in the class index. If set to NO only the inherited external classes +# will be listed. + +ALLEXTERNALS = NO + +# If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed +# in the modules index. If set to NO, only the current project's groups will +# be listed. + +EXTERNAL_GROUPS = YES + +# The PERL_PATH should be the absolute path and name of the perl script +# interpreter (i.e. the result of `which perl'). + +PERL_PATH = /usr/bin/perl + +#--------------------------------------------------------------------------- +# Configuration options related to the dot tool +#--------------------------------------------------------------------------- + +# If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will +# generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base +# or super classes. Setting the tag to NO turns the diagrams off. Note that +# this option is superseded by the HAVE_DOT option below. This is only a +# fallback. It is recommended to install and use dot, since it yields more +# powerful graphs. + +CLASS_DIAGRAMS = YES + +# You can define message sequence charts within doxygen comments using the \msc +# command. Doxygen will then run the mscgen tool (see +# http://www.mcternan.me.uk/mscgen/) to produce the chart and insert it in the +# documentation. The MSCGEN_PATH tag allows you to specify the directory where +# the mscgen tool resides. If left empty the tool is assumed to be found in the +# default search path. + +MSCGEN_PATH = + +# If set to YES, the inheritance and collaboration graphs will hide +# inheritance and usage relations if the target is undocumented +# or is not a class. + +HIDE_UNDOC_RELATIONS = YES + +# If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is +# available from the path. This tool is part of Graphviz, a graph visualization +# toolkit from AT&T and Lucent Bell Labs. The other options in this section +# have no effect if this option is set to NO (the default) + +HAVE_DOT = NO + +# By default doxygen will write a font called FreeSans.ttf to the output +# directory and reference it in all dot files that doxygen generates. This +# font does not include all possible unicode characters however, so when you need +# these (or just want a differently looking font) you can specify the font name +# using DOT_FONTNAME. You need need to make sure dot is able to find the font, +# which can be done by putting it in a standard location or by setting the +# DOTFONTPATH environment variable or by setting DOT_FONTPATH to the directory +# containing the font. + +DOT_FONTNAME = FreeSans + +# By default doxygen will tell dot to use the output directory to look for the +# FreeSans.ttf font (which doxygen will put there itself). If you specify a +# different font using DOT_FONTNAME you can set the path where dot +# can find it using this tag. + +DOT_FONTPATH = + +# If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen +# will generate a graph for each documented class showing the direct and +# indirect inheritance relations. Setting this tag to YES will force the +# the CLASS_DIAGRAMS tag to NO. + +CLASS_GRAPH = YES + +# If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen +# will generate a graph for each documented class showing the direct and +# indirect implementation dependencies (inheritance, containment, and +# class references variables) of the class with other documented classes. + +COLLABORATION_GRAPH = YES + +# If the GROUP_GRAPHS and HAVE_DOT tags are set to YES then doxygen +# will generate a graph for groups, showing the direct groups dependencies + +GROUP_GRAPHS = YES + +# If the UML_LOOK tag is set to YES doxygen will generate inheritance and +# collaboration diagrams in a style similar to the OMG's Unified Modeling +# Language. + +UML_LOOK = NO + +# If set to YES, the inheritance and collaboration graphs will show the +# relations between templates and their instances. + +TEMPLATE_RELATIONS = NO + +# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT +# tags are set to YES then doxygen will generate a graph for each documented +# file showing the direct and indirect include dependencies of the file with +# other documented files. + +INCLUDE_GRAPH = YES + +# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and +# HAVE_DOT tags are set to YES then doxygen will generate a graph for each +# documented header file showing the documented files that directly or +# indirectly include this file. + +INCLUDED_BY_GRAPH = YES + +# If the CALL_GRAPH and HAVE_DOT options are set to YES then +# doxygen will generate a call dependency graph for every global function +# or class method. Note that enabling this option will significantly increase +# the time of a run. So in most cases it will be better to enable call graphs +# for selected functions only using the \callgraph command. + +CALL_GRAPH = NO + +# If the CALLER_GRAPH and HAVE_DOT tags are set to YES then +# doxygen will generate a caller dependency graph for every global function +# or class method. Note that enabling this option will significantly increase +# the time of a run. So in most cases it will be better to enable caller +# graphs for selected functions only using the \callergraph command. + +CALLER_GRAPH = NO + +# If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen +# will graphical hierarchy of all classes instead of a textual one. + +GRAPHICAL_HIERARCHY = YES + +# If the DIRECTORY_GRAPH, SHOW_DIRECTORIES and HAVE_DOT tags are set to YES +# then doxygen will show the dependencies a directory has on other directories +# in a graphical way. The dependency relations are determined by the #include +# relations between the files in the directories. + +DIRECTORY_GRAPH = YES + +# The DOT_IMAGE_FORMAT tag can be used to set the image format of the images +# generated by dot. Possible values are png, jpg, or gif +# If left blank png will be used. + +DOT_IMAGE_FORMAT = png + +# The tag DOT_PATH can be used to specify the path where the dot tool can be +# found. If left blank, it is assumed the dot tool can be found in the path. + +DOT_PATH = + +# The DOTFILE_DIRS tag can be used to specify one or more directories that +# contain dot files that are included in the documentation (see the +# \dotfile command). + +DOTFILE_DIRS = + +# The DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of +# nodes that will be shown in the graph. If the number of nodes in a graph +# becomes larger than this value, doxygen will truncate the graph, which is +# visualized by representing a node as a red box. Note that doxygen if the +# number of direct children of the root node in a graph is already larger than +# DOT_GRAPH_MAX_NODES then the graph will not be shown at all. Also note +# that the size of a graph can be further restricted by MAX_DOT_GRAPH_DEPTH. + +DOT_GRAPH_MAX_NODES = 50 + +# The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the +# graphs generated by dot. A depth value of 3 means that only nodes reachable +# from the root by following a path via at most 3 edges will be shown. Nodes +# that lay further from the root node will be omitted. Note that setting this +# option to 1 or 2 may greatly reduce the computation time needed for large +# code bases. Also note that the size of a graph can be further restricted by +# DOT_GRAPH_MAX_NODES. Using a depth of 0 means no depth restriction. + +MAX_DOT_GRAPH_DEPTH = 0 + +# Set the DOT_TRANSPARENT tag to YES to generate images with a transparent +# background. This is enabled by default, which results in a transparent +# background. Warning: Depending on the platform used, enabling this option +# may lead to badly anti-aliased labels on the edges of a graph (i.e. they +# become hard to read). + +DOT_TRANSPARENT = YES + +# Set the DOT_MULTI_TARGETS tag to YES allow dot to generate multiple output +# files in one run (i.e. multiple -o and -T options on the command line). This +# makes dot run faster, but since only newer versions of dot (>1.8.10) +# support this, this feature is disabled by default. + +DOT_MULTI_TARGETS = NO + +# If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will +# generate a legend page explaining the meaning of the various boxes and +# arrows in the dot generated graphs. + +GENERATE_LEGEND = YES + +# If the DOT_CLEANUP tag is set to YES (the default) Doxygen will +# remove the intermediate dot files that are used to generate +# the various graphs. + +DOT_CLEANUP = YES + +#--------------------------------------------------------------------------- +# Configuration::additions related to the search engine +#--------------------------------------------------------------------------- + +# The SEARCHENGINE tag specifies whether or not a search engine should be +# used. If set to NO the values of all tags below this one will be ignored. + +SEARCHENGINE = NO diff --git a/Master/texmf-dist/doc/support/lua2dox/INSTALL b/Master/texmf-dist/doc/support/lua2dox/INSTALL new file mode 100644 index 00000000000..9a1cc4886af --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/INSTALL @@ -0,0 +1,42 @@ +////////////////////// +// INSTALL +////////////////////// + +Only tested for linux, but should work for any unix-like OS. + +For other OS you need to figure it out yourself. +If you do, then please email me with the code/suggestions. + +/////////////// +// requirements +/////////////// +A reasonably recent: doxygen and luatex. + +Whilst luatex isn't strictly required to make it run for TeX users +we are more likely to have a recent version (via texlive) of texlua +rather than relying on you, possibly aging, distro's lua. + +/////////////// +linux/unix: +/////////////// + +1) manually check if lua2dox_lua runs on your system. + +From the commandline run "./lua2dox_lua --help". +If it runs and produces a sensible result then it probably works. + +2) Manually pick an appropriate directory for this system. + +Make this new directory and copy/mv all these files into there. +If you are installing it as a personal app then put it somewhere in your +userspace. For system-wide: ask sysadmin. + +3) Run "install.sh". +This makes the links to the active code. + +Default is to put in "~/bin". For system-wide: ask sysadmin. + +Erm, that's about it. + +Simon + diff --git a/Master/texmf-dist/doc/support/lua2dox/README b/Master/texmf-dist/doc/support/lua2dox/README new file mode 100644 index 00000000000..eefefecd7d1 --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/README @@ -0,0 +1,17 @@ +########## +lua2dox_lua + +This is a hack to enable doxygen to document lua. + +It uses the wellknown doxygen filter mechanism to fool doxygen into reading foreign languages. + +If this works for you then enjoy. + +Files: + INSTALL -- help with installation + lua2dox-refm.pdf -- more extensive documentation + +Simon Dales +18/5/2012 + +## \ No newline at end of file diff --git a/Master/texmf-dist/doc/support/lua2dox/docs/html/doxygen.css b/Master/texmf-dist/doc/support/lua2dox/docs/html/doxygen.css new file mode 100644 index 00000000000..22c484301dd --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/docs/html/doxygen.css @@ -0,0 +1,473 @@ +BODY,H1,H2,H3,H4,H5,H6,P,CENTER,TD,TH,UL,DL,DIV { + font-family: Geneva, Arial, Helvetica, sans-serif; +} +BODY,TD { + font-size: 90%; +} +H1 { + text-align: center; + font-size: 160%; +} +H2 { + font-size: 120%; +} +H3 { + font-size: 100%; +} +CAPTION { + font-weight: bold +} +DIV.qindex { + width: 100%; + background-color: #e8eef2; + border: 1px solid #84b0c7; + text-align: center; + margin: 2px; + padding: 2px; + line-height: 140%; +} +DIV.navpath { + width: 100%; + background-color: #e8eef2; + border: 1px solid #84b0c7; + text-align: center; + margin: 2px; + padding: 2px; + line-height: 140%; +} +DIV.navtab { + background-color: #e8eef2; + border: 1px solid #84b0c7; + text-align: center; + margin: 2px; + margin-right: 15px; + padding: 2px; +} +TD.navtab { + font-size: 70%; +} +A.qindex { + text-decoration: none; + font-weight: bold; + color: #1A419D; +} +A.qindex:visited { + text-decoration: none; + font-weight: bold; + color: #1A419D +} +A.qindex:hover { + text-decoration: none; + background-color: #ddddff; +} +A.qindexHL { + text-decoration: none; + font-weight: bold; + background-color: #6666cc; + color: #ffffff; + border: 1px double #9295C2; +} +A.qindexHL:hover { + text-decoration: none; + background-color: #6666cc; + color: #ffffff; +} +A.qindexHL:visited { + text-decoration: none; + background-color: #6666cc; + color: #ffffff +} +A.el { + text-decoration: none; + font-weight: bold +} +A.elRef { + font-weight: bold +} +A.code:link { + text-decoration: none; + font-weight: normal; + color: #0000FF +} +A.code:visited { + text-decoration: none; + font-weight: normal; + color: #0000FF +} +A.codeRef:link { + font-weight: normal; + color: #0000FF +} +A.codeRef:visited { + font-weight: normal; + color: #0000FF +} +A:hover { + text-decoration: none; + background-color: #f2f2ff +} +DL.el { + margin-left: -1cm +} +.fragment { + font-family: monospace, fixed; + font-size: 95%; +} +PRE.fragment { + border: 1px solid #CCCCCC; + background-color: #f5f5f5; + margin-top: 4px; + margin-bottom: 4px; + margin-left: 2px; + margin-right: 8px; + padding-left: 6px; + padding-right: 6px; + padding-top: 4px; + padding-bottom: 4px; +} +DIV.ah { + background-color: black; + font-weight: bold; + color: #ffffff; + margin-bottom: 3px; + margin-top: 3px +} + +DIV.groupHeader { + margin-left: 16px; + margin-top: 12px; + margin-bottom: 6px; + font-weight: bold; +} +DIV.groupText { + margin-left: 16px; + font-style: italic; + font-size: 90% +} +BODY { + background: white; + color: black; + margin-right: 20px; + margin-left: 20px; +} +TD.indexkey { + background-color: #e8eef2; + font-weight: bold; + padding-right : 10px; + padding-top : 2px; + padding-left : 10px; + padding-bottom : 2px; + margin-left : 0px; + margin-right : 0px; + margin-top : 2px; + margin-bottom : 2px; + border: 1px solid #CCCCCC; +} +TD.indexvalue { + background-color: #e8eef2; + font-style: italic; + padding-right : 10px; + padding-top : 2px; + padding-left : 10px; + padding-bottom : 2px; + margin-left : 0px; + margin-right : 0px; + margin-top : 2px; + margin-bottom : 2px; + border: 1px solid #CCCCCC; +} +TR.memlist { + background-color: #f0f0f0; +} +P.formulaDsp { + text-align: center; +} +IMG.formulaDsp { +} +IMG.formulaInl { + vertical-align: middle; +} +SPAN.keyword { color: #008000 } +SPAN.keywordtype { color: #604020 } +SPAN.keywordflow { color: #e08000 } +SPAN.comment { color: #800000 } +SPAN.preprocessor { color: #806020 } +SPAN.stringliteral { color: #002080 } +SPAN.charliteral { color: #008080 } +SPAN.vhdldigit { color: #ff00ff } +SPAN.vhdlchar { color: #000000 } +SPAN.vhdlkeyword { color: #700070 } +SPAN.vhdllogic { color: #ff0000 } + +.mdescLeft { + padding: 0px 8px 4px 8px; + font-size: 80%; + font-style: italic; + background-color: #FAFAFA; + border-top: 1px none #E0E0E0; + border-right: 1px none #E0E0E0; + border-bottom: 1px none #E0E0E0; + border-left: 1px none #E0E0E0; + margin: 0px; +} +.mdescRight { + padding: 0px 8px 4px 8px; + font-size: 80%; + font-style: italic; + background-color: #FAFAFA; + border-top: 1px none #E0E0E0; + border-right: 1px none #E0E0E0; + border-bottom: 1px none #E0E0E0; + border-left: 1px none #E0E0E0; + margin: 0px; +} +.memItemLeft { + padding: 1px 0px 0px 8px; + margin: 4px; + border-top-width: 1px; + border-right-width: 1px; + border-bottom-width: 1px; + border-left-width: 1px; + border-top-color: #E0E0E0; + border-right-color: #E0E0E0; + border-bottom-color: #E0E0E0; + border-left-color: #E0E0E0; + border-top-style: solid; + border-right-style: none; + border-bottom-style: none; + border-left-style: none; + background-color: #FAFAFA; + font-size: 80%; +} +.memItemRight { + padding: 1px 8px 0px 8px; + margin: 4px; + border-top-width: 1px; + border-right-width: 1px; + border-bottom-width: 1px; + border-left-width: 1px; + border-top-color: #E0E0E0; + border-right-color: #E0E0E0; + border-bottom-color: #E0E0E0; + border-left-color: #E0E0E0; + border-top-style: solid; + border-right-style: none; + border-bottom-style: none; + border-left-style: none; + background-color: #FAFAFA; + font-size: 80%; +} +.memTemplItemLeft { + padding: 1px 0px 0px 8px; + margin: 4px; + border-top-width: 1px; + border-right-width: 1px; + border-bottom-width: 1px; + border-left-width: 1px; + border-top-color: #E0E0E0; + border-right-color: #E0E0E0; + border-bottom-color: #E0E0E0; + border-left-color: #E0E0E0; + border-top-style: none; + border-right-style: none; + border-bottom-style: none; + border-left-style: none; + background-color: #FAFAFA; + font-size: 80%; +} +.memTemplItemRight { + padding: 1px 8px 0px 8px; + margin: 4px; + border-top-width: 1px; + border-right-width: 1px; + border-bottom-width: 1px; + border-left-width: 1px; + border-top-color: #E0E0E0; + border-right-color: #E0E0E0; + border-bottom-color: #E0E0E0; + border-left-color: #E0E0E0; + border-top-style: none; + border-right-style: none; + border-bottom-style: none; + border-left-style: none; + background-color: #FAFAFA; + font-size: 80%; +} +.memTemplParams { + padding: 1px 0px 0px 8px; + margin: 4px; + border-top-width: 1px; + border-right-width: 1px; + border-bottom-width: 1px; + border-left-width: 1px; + border-top-color: #E0E0E0; + border-right-color: #E0E0E0; + border-bottom-color: #E0E0E0; + border-left-color: #E0E0E0; + border-top-style: solid; + border-right-style: none; + border-bottom-style: none; + border-left-style: none; + color: #606060; + background-color: #FAFAFA; + font-size: 80%; +} +.search { + color: #003399; + font-weight: bold; +} +FORM.search { + margin-bottom: 0px; + margin-top: 0px; +} +INPUT.search { + font-size: 75%; + color: #000080; + font-weight: normal; + background-color: #e8eef2; +} +TD.tiny { + font-size: 75%; +} +a { + color: #1A41A8; +} +a:visited { + color: #2A3798; +} +.dirtab { + padding: 4px; + border-collapse: collapse; + border: 1px solid #84b0c7; +} +TH.dirtab { + background: #e8eef2; + font-weight: bold; +} +HR { + height: 1px; + border: none; + border-top: 1px solid black; +} + +/* Style for detailed member documentation */ +.memtemplate { + font-size: 80%; + color: #606060; + font-weight: normal; + margin-left: 3px; +} +.memnav { + background-color: #e8eef2; + border: 1px solid #84b0c7; + text-align: center; + margin: 2px; + margin-right: 15px; + padding: 2px; +} +.memitem { + padding: 4px; + background-color: #eef3f5; + border-width: 1px; + border-style: solid; + border-color: #dedeee; + -moz-border-radius: 8px 8px 8px 8px; +} +.memname { + white-space: nowrap; + font-weight: bold; +} +.memdoc{ + padding-left: 10px; +} +.memproto { + background-color: #d5e1e8; + width: 100%; + border-width: 1px; + border-style: solid; + border-color: #84b0c7; + font-weight: bold; + -moz-border-radius: 8px 8px 8px 8px; +} +.paramkey { + text-align: right; +} +.paramtype { + white-space: nowrap; +} +.paramname { + color: #602020; + font-style: italic; + white-space: nowrap; +} +/* End Styling for detailed member documentation */ + +/* for the tree view */ +.ftvtree { + font-family: sans-serif; + margin:0.5em; +} +/* these are for tree view when used as main index */ +.directory { + font-size: 9pt; + font-weight: bold; +} +.directory h3 { + margin: 0px; + margin-top: 1em; + font-size: 11pt; +} + +/* The following two styles can be used to replace the root node title */ +/* with an image of your choice. Simply uncomment the next two styles, */ +/* specify the name of your image and be sure to set 'height' to the */ +/* proper pixel height of your image. */ + +/* .directory h3.swap { */ +/* height: 61px; */ +/* background-repeat: no-repeat; */ +/* background-image: url("yourimage.gif"); */ +/* } */ +/* .directory h3.swap span { */ +/* display: none; */ +/* } */ + +.directory > h3 { + margin-top: 0; +} +.directory p { + margin: 0px; + white-space: nowrap; +} +.directory div { + display: none; + margin: 0px; +} +.directory img { + vertical-align: -30%; +} +/* these are for tree view when not used as main index */ +.directory-alt { + font-size: 100%; + font-weight: bold; +} +.directory-alt h3 { + margin: 0px; + margin-top: 1em; + font-size: 11pt; +} +.directory-alt > h3 { + margin-top: 0; +} +.directory-alt p { + margin: 0px; + white-space: nowrap; +} +.directory-alt div { + display: none; + margin: 0px; +} +.directory-alt img { + vertical-align: -30%; +} + diff --git a/Master/texmf-dist/doc/support/lua2dox/docs/html/doxygen.png b/Master/texmf-dist/doc/support/lua2dox/docs/html/doxygen.png new file mode 100644 index 00000000000..f0a274bbaff Binary files /dev/null and b/Master/texmf-dist/doc/support/lua2dox/docs/html/doxygen.png differ diff --git a/Master/texmf-dist/doc/support/lua2dox/docs/html/files.html b/Master/texmf-dist/doc/support/lua2dox/docs/html/files.html new file mode 100644 index 00000000000..09843a483b7 --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/docs/html/files.html @@ -0,0 +1,31 @@ + + +Lua2dox.lua: File Index + + + + + +
+

File List

Here is a list of all files with brief descriptions: + +
lua2dox.lua [code]Hack lua2dox converter
+
+
Generated on Wed Jul 4 18:43:04 2012 for Lua2dox.lua by  + +doxygen 1.5.6
+ + diff --git a/Master/texmf-dist/doc/support/lua2dox/docs/html/globals.html b/Master/texmf-dist/doc/support/lua2dox/docs/html/globals.html new file mode 100644 index 00000000000..c0ba18117fa --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/docs/html/globals.html @@ -0,0 +1,92 @@ + + +Lua2dox.lua: Class Members + + + + + +
+Here is a list of all file members with links to the files they belong to: +

+

+
+
Generated on Wed Jul 4 18:43:04 2012 for Lua2dox.lua by  + +doxygen 1.5.6
+ + diff --git a/Master/texmf-dist/doc/support/lua2dox/docs/html/globals_func.html b/Master/texmf-dist/doc/support/lua2dox/docs/html/globals_func.html new file mode 100644 index 00000000000..1ff826f57c1 --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/docs/html/globals_func.html @@ -0,0 +1,92 @@ + + +Lua2dox.lua: Class Members + + + + + +
+  +

+

+
+
Generated on Wed Jul 4 18:43:04 2012 for Lua2dox.lua by  + +doxygen 1.5.6
+ + diff --git a/Master/texmf-dist/doc/support/lua2dox/docs/html/index.html b/Master/texmf-dist/doc/support/lua2dox/docs/html/index.html new file mode 100644 index 00000000000..4a3774bdb25 --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/docs/html/index.html @@ -0,0 +1,43 @@ + + +Lua2dox.lua: Main Page + + + + + +
+

Lua2dox.lua Documentation

+

+

0.1 20120704

A hack lua2dox converter Version 0.1

+This lets us make Doxygen output some documentation to let us develop this code.

+It is partially cribbed from the functionality of lua2dox (http://search.cpan.org/~alec/Doxygen-Lua-0.02/lib/Doxygen/Lua.pm). Found on CPAN when looking for something else; kinda handy.

+Improved from lua2dox to make the doxygen output more friendly. Also it runs faster in lua rather than Perl.

+Because this Perl based system is called "lua2dox"., I have decided to add ".lua" to the name to keep the two separate.

+0. Ensure doxygen is installed on your system and that you are familiar with its use. Best is to try to make and document some simple C/C++/PHP to see what it produces.

+1. Run "lua2dox_lua -g" to create a default Doxyfile.

+Then alter it to let it recognise lua. Add the two following lines:

+FILE_PATTERNS = *.lua

+FILTER_PATTERNS = *.lua=lua2dox_filter

+Either add them to the end or find the appropriate entry in Doxyfile.

+2. When Doxyfile is edited run as "lua2dox_lua"

+When reading source with classes multiple passes are needed. Each pass generates a list of member functions (as a file) that were found on this pass. This list is read in on the next pass. If the class+methods haven't changed this time then you only need to run it once, else run twice.

+The core function reads the input file (filename or stdin) and outputs some pseudo C-ish language. It only has to be good enough for doxygen to see it as legal. Therefore our lua interpreter is fairly limited, but "good enough".

+One limitation is that each line is treated separately (except for long comments). The implication is that class and function declarations must be on the same line. Some functions can have their parameter lists extended over multiple lines to make it look neat. Managing this where there are also some comments is a bit more coding than I want to do at this stage, so it will probably not document accurately if we do do this.

+However I have put in a hack that will insert the "missing" close paren. The effect is that you will get the function documented, but not with the parameter list you might expect.

+Installation:

+Here for linux or unix-like, for any other OS you need to refer to other documentation.

+This file is "lua2dox.lua". It gets called by "lua2dox_lua". Somewhere in your path (e.g. "~/bin" or "/usr/local/bin") put two links to "lua2dox_lua". Names to use are "lua2dox_lua" and "lua2dox_filter".

+Call it as "lua2dox_lua" and the filter that gets called by doxygen is "lua2dox_filter".

+
Generated on Wed Jul 4 18:43:04 2012 for Lua2dox.lua by  + +doxygen 1.5.6
+ + diff --git a/Master/texmf-dist/doc/support/lua2dox/docs/html/lua2dox_8lua-source.html b/Master/texmf-dist/doc/support/lua2dox/docs/html/lua2dox_8lua-source.html new file mode 100644 index 00000000000..1fd59491e0e --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/docs/html/lua2dox_8lua-source.html @@ -0,0 +1,638 @@ + + +Lua2dox.lua: lua2dox.lua Source File + + + + + +
Generated on Wed Jul 4 18:43:04 2012 for Lua2dox.lua by  + +doxygen 1.5.6
+ + diff --git a/Master/texmf-dist/doc/support/lua2dox/docs/html/lua2dox_8lua.html b/Master/texmf-dist/doc/support/lua2dox/docs/html/lua2dox_8lua.html new file mode 100644 index 00000000000..3d6ae4e376c --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/docs/html/lua2dox_8lua.html @@ -0,0 +1,891 @@ + + +Lua2dox.lua: lua2dox.lua File Reference + + + + + +
+

lua2dox.lua File Reference

a hack lua2dox converter More... +

+ +

+Go to the source code of this file. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

Functions

local function TApp_get_appname ()
 get appname
local function TApp_lua2dox (FileContents)
 hack converter from lua to a pseudoC-ish language for doxygen
local function TApp_run_doxygen (AppTimestamp, Argv, CommentaryFiles)
 run doxygen for one
local function TApp_run_filter (AppTimestamp, Filename, CommentaryFiles)
 run the filter
local function TClassList_method_add (Klass, Method)
 add a method to list of known methods
local function TClassList_method_get (Klass)
 get methods
local function TClock_GetTimeNow ()
 get the current time
local function TClock_getTimeStamp ()
 get a timestamp
local function TCommandline_getargv ()
 setup the commandline now
local function TCommandline_setup ()
 setup/parse the commandline
local function TCommentary_addMethod (Klass, Method)
 method to save file
local function TCommentary_close ()
 close the methods save file
local function TCommentary_open (Filename, InputLuaFilename)
 open the commentary save file
local function TCommentary_readFileContents (Filename)
 read stuff from save file
local function TCommentary_writeln (Str)
 write to output file
local function TConfig_get (Key, Default)
 Gets a config val.
local function TConfig_set (Key, Val)
 sets a config val
local function TIO_out2stream (Line)
 output line to stream
local function TIO_out2stream_commented (Line, Prefix, Suffix)
 suppress line
local function TIO_showError (Err, Str)
 show error to stdout
local function TIO_write (Str)
 write to stdout
local function TIO_writeln (Str)
 write to stdout
local function TOS_fileExists (Filename)
 does file exist?
local function TOS_system (Cmd)
 run system command
local function TString_removeCommentFromLine (Line)
 trim comment off end of string
local function TString_split (Str, Pattern)
 split a string
local function TString_trim (Str)
 trims a string from both ends
+


Detailed Description

+a hack lua2dox converter +

+ +

Definition in file lua2dox.lua.

+

Function Documentation

+ +
+
+ + + + + + + + +
local function TApp_get_appname (  ) 
+
+
+ +

+get appname +

+ +

Definition at line 378 of file lua2dox.lua.

+ +
+

+ +

+
+ + + + + + + + + +
local function TApp_lua2dox (FileContents   ) 
+
+
+ +

+hack converter from lua to a pseudoC-ish language for doxygen +

+This is a hack to make lua readable to doxygen.

+It works well enough to document functions/methods and classes, but not assignments. Our pseudo-C gets confused if we allow assginments to be shown. Because these are less interesting than class/functions/methods I have decided to live with this limitation. +

Definition at line 391 of file lua2dox.lua.

+ +
+

+ +

+
+ + + + + + + + + + + + + + + + + + + + + + + + +
local function TApp_run_doxygen (AppTimestamp ,
Argv ,
CommentaryFiles  
)
+
+
+ +

+run doxygen for one +

+

Parameters:
+ + + + +
AppTimestamp application + timestamp for this run
Argv commandline for this run
CommentaryFiles names of commentary files
+
+
Returns:
err or nil
+ +

Definition at line 558 of file lua2dox.lua.

+ +
+

+ +

+
+ + + + + + + + + + + + + + + + + + + + + + + + +
local function TApp_run_filter (AppTimestamp ,
Filename ,
CommentaryFiles  
)
+
+
+ +

+run the filter +

+

Parameters:
+ + + + +
AppTimestamp application + timestamp for this run
Filename the filename or if nil stdin
CommentaryFiles names of commentary files
+
+
Returns:
err or nil
+ +

Definition at line 519 of file lua2dox.lua.

+ +
+

+ +

+
+ + + + + + + + + + + + + + + + + + +
local function TClassList_method_add (Klass ,
Method  
)
+
+
+ +

+add a method to list of known methods +

+ +

Definition at line 236 of file lua2dox.lua.

+ +
+

+ +

+
+ + + + + + + + + +
local function TClassList_method_get (Klass   ) 
+
+
+ +

+get methods +

+ +

Definition at line 231 of file lua2dox.lua.

+ +
+

+ +

+
+ + + + + + + + +
local function TClock_GetTimeNow (  ) 
+
+
+ +

+get the current time +

+ +

Definition at line 167 of file lua2dox.lua.

+ +
+

+ +

+
+ + + + + + + + +
local function TClock_getTimeStamp (  ) 
+
+
+ +

+get a timestamp +

+not strictly necessary here but lets us put a timestamp on the end of the output stream. Note that doxygen won't read this, and being off the end of the true file length (num lines), it will have no effect. However it lets us check the output file tail when debugging. +

Definition at line 182 of file lua2dox.lua.

+ +
+

+ +

+
+ + + + + + + + +
local function TCommandline_getargv (  ) 
+
+
+ +

+setup the commandline now +

+get commandline args +

Definition at line 373 of file lua2dox.lua.

+ +
+

+ +

+
+ + + + + + + + +
local function TCommandline_setup (  ) 
+
+
+ +

+setup/parse the commandline +

+ +

Definition at line 352 of file lua2dox.lua.

+ +
+

+ +

+
+ + + + + + + + + + + + + + + + + + +
local function TCommentary_addMethod (Klass ,
Method  
)
+
+
+ +

+method to save file +

+ +

Definition at line 316 of file lua2dox.lua.

+ +
+

+ +

+
+ + + + + + + + +
local function TCommentary_close (  ) 
+
+
+ +

+close the methods save file +

+ +

Definition at line 266 of file lua2dox.lua.

+ +
+

+ +

+
+ + + + + + + + + + + + + + + + + + +
local function TCommentary_open (Filename ,
InputLuaFilename  
)
+
+
+ +

+open the commentary save file +

+ +

Definition at line 257 of file lua2dox.lua.

+ +
+

+ +

+
+ + + + + + + + + +
local function TCommentary_readFileContents (Filename   ) 
+
+
+ +

+read stuff from save file +

+ +

Definition at line 275 of file lua2dox.lua.

+ +
+

+ +

+
+ + + + + + + + + +
local function TCommentary_writeln (Str   ) 
+
+
+ +

+write to output file +

+ +

Definition at line 249 of file lua2dox.lua.

+ +
+

+ +

+
+ + + + + + + + + + + + + + + + + + +
local function TConfig_get (Key ,
Default  
)
+
+
+ +

+Gets a config val. +

+ +

Definition at line 99 of file lua2dox.lua.

+ +
+

+ +

+
+ + + + + + + + + + + + + + + + + + +
local function TConfig_set (Key ,
Val  
)
+
+
+ +

+sets a config val +

+ +

Definition at line 108 of file lua2dox.lua.

+ +
+

+ +

+
+ + + + + + + + + +
local function TIO_out2stream (Line   ) 
+
+
+ +

+output line to stream +

+Wraps IO_writeln() +

Definition at line 331 of file lua2dox.lua.

+ +
+

+ +

+
+ + + + + + + + + + + + + + + + + + + + + + + + +
local function TIO_out2stream_commented (Line ,
Prefix ,
Suffix  
)
+
+
+ +

+suppress line +

+ +

Definition at line 336 of file lua2dox.lua.

+ +
+

+ +

+
+ + + + + + + + + + + + + + + + + + +
local function TIO_showError (Err ,
Str  
)
+
+
+ +

+show error to stdout +

+writelns Str (if not nil) and then an eoln. +

Definition at line 134 of file lua2dox.lua.

+ +
+

+ +

+
+ + + + + + + + + +
local function TIO_write (Str   ) 
+
+
+ +

+write to stdout +

+writes Str (if not nil) +

Definition at line 115 of file lua2dox.lua.

+ +
+

+ +

+
+ + + + + + + + + +
local function TIO_writeln (Str   ) 
+
+
+ +

+write to stdout +

+writelns Str (if not nil) and then an eoln. +

Definition at line 124 of file lua2dox.lua.

+ +
+

+ +

+
+ + + + + + + + + +
local function TOS_fileExists (Filename   ) 
+
+
+ +

+does file exist? +

+ +

Definition at line 157 of file lua2dox.lua.

+ +
+

+ +

+
+ + + + + + + + + +
local function TOS_system (Cmd   ) 
+
+
+ +

+run system command +

+ +

Definition at line 146 of file lua2dox.lua.

+ +
+

+ +

+
+ + + + + + + + + +
local function TString_removeCommentFromLine (Line   ) 
+
+
+ +

+trim comment off end of string +

+If the string has a comment on the end, this trims it off. +

Definition at line 221 of file lua2dox.lua.

+ +
+

+ +

+
+ + + + + + + + + + + + + + + + + + +
local function TString_split (Str ,
Pattern  
)
+
+
+ +

+split a string +

+

Parameters:
+ + + +
Str 
Pattern 
+
+
Returns:
table of string fragments
+ +

Definition at line 198 of file lua2dox.lua.

+ +
+

+ +

+
+ + + + + + + + + +
local function TString_trim (Str   ) 
+
+
+ +

+trims a string from both ends +

+ +

Definition at line 189 of file lua2dox.lua.

+ +
+

+

+
Generated on Wed Jul 4 18:43:04 2012 for Lua2dox.lua by  + +doxygen 1.5.6
+ + diff --git a/Master/texmf-dist/doc/support/lua2dox/docs/html/tab_b.gif b/Master/texmf-dist/doc/support/lua2dox/docs/html/tab_b.gif new file mode 100644 index 00000000000..0d623483ffd Binary files /dev/null and b/Master/texmf-dist/doc/support/lua2dox/docs/html/tab_b.gif differ diff --git a/Master/texmf-dist/doc/support/lua2dox/docs/html/tab_l.gif b/Master/texmf-dist/doc/support/lua2dox/docs/html/tab_l.gif new file mode 100644 index 00000000000..9b1e6337c92 Binary files /dev/null and b/Master/texmf-dist/doc/support/lua2dox/docs/html/tab_l.gif differ diff --git a/Master/texmf-dist/doc/support/lua2dox/docs/html/tab_r.gif b/Master/texmf-dist/doc/support/lua2dox/docs/html/tab_r.gif new file mode 100644 index 00000000000..ce9dd9f533c Binary files /dev/null and b/Master/texmf-dist/doc/support/lua2dox/docs/html/tab_r.gif differ diff --git a/Master/texmf-dist/doc/support/lua2dox/docs/html/tabs.css b/Master/texmf-dist/doc/support/lua2dox/docs/html/tabs.css new file mode 100644 index 00000000000..95f00a91da3 --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/docs/html/tabs.css @@ -0,0 +1,102 @@ +/* tabs styles, based on http://www.alistapart.com/articles/slidingdoors */ + +DIV.tabs +{ + float : left; + width : 100%; + background : url("tab_b.gif") repeat-x bottom; + margin-bottom : 4px; +} + +DIV.tabs UL +{ + margin : 0px; + padding-left : 10px; + list-style : none; +} + +DIV.tabs LI, DIV.tabs FORM +{ + display : inline; + margin : 0px; + padding : 0px; +} + +DIV.tabs FORM +{ + float : right; +} + +DIV.tabs A +{ + float : left; + background : url("tab_r.gif") no-repeat right top; + border-bottom : 1px solid #84B0C7; + font-size : x-small; + font-weight : bold; + text-decoration : none; +} + +DIV.tabs A:hover +{ + background-position: 100% -150px; +} + +DIV.tabs A:link, DIV.tabs A:visited, +DIV.tabs A:active, DIV.tabs A:hover +{ + color: #1A419D; +} + +DIV.tabs SPAN +{ + float : left; + display : block; + background : url("tab_l.gif") no-repeat left top; + padding : 5px 9px; + white-space : nowrap; +} + +DIV.tabs INPUT +{ + float : right; + display : inline; + font-size : 1em; +} + +DIV.tabs TD +{ + font-size : x-small; + font-weight : bold; + text-decoration : none; +} + + + +/* Commented Backslash Hack hides rule from IE5-Mac \*/ +DIV.tabs SPAN {float : none;} +/* End IE5-Mac hack */ + +DIV.tabs A:hover SPAN +{ + background-position: 0% -150px; +} + +DIV.tabs LI.current A +{ + background-position: 100% -150px; + border-width : 0px; +} + +DIV.tabs LI.current SPAN +{ + background-position: 0% -150px; + padding-bottom : 6px; +} + +DIV.navpath +{ + background : none; + border : none; + border-bottom : 1px solid #84B0C7; +} diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/lua/Doxyfile b/Master/texmf-dist/doc/support/lua2dox/examples/lua/Doxyfile new file mode 100644 index 00000000000..07a22d3f4eb --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/examples/lua/Doxyfile @@ -0,0 +1,1421 @@ +# Doxyfile 1.5.6 + +# This file describes the settings to be used by the documentation system +# doxygen (www.doxygen.org) for a project +# +# All text after a hash (#) is considered a comment and will be ignored +# The format is: +# TAG = value [value, ...] +# For lists items can also be appended using: +# TAG += value [value, ...] +# Values that contain spaces should be placed between quotes (" ") + +#--------------------------------------------------------------------------- +# Project related configuration options +#--------------------------------------------------------------------------- + +# This tag specifies the encoding used for all characters in the config file +# that follow. The default is UTF-8 which is also the encoding used for all +# text before the first occurrence of this tag. Doxygen uses libiconv (or the +# iconv built into libc) for the transcoding. See +# http://www.gnu.org/software/libiconv for the list of possible encodings. + +DOXYFILE_ENCODING = UTF-8 + +# The PROJECT_NAME tag is a single word (or a sequence of words surrounded +# by quotes) that should identify the project. + +PROJECT_NAME = "Sample Code" + +# The PROJECT_NUMBER tag can be used to enter a project or revision number. +# This could be handy for archiving the generated documentation or +# if some version control system is used. + +PROJECT_NUMBER = "0.1 20120518" + +# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) +# base path where the generated documentation will be put. +# If a relative path is entered, it will be relative to the location +# where doxygen was started. If left blank the current directory will be used. + +OUTPUT_DIRECTORY = docs + +# If the CREATE_SUBDIRS tag is set to YES, then doxygen will create +# 4096 sub-directories (in 2 levels) under the output directory of each output +# format and will distribute the generated files over these directories. +# Enabling this option can be useful when feeding doxygen a huge amount of +# source files, where putting all generated files in the same directory would +# otherwise cause performance problems for the file system. + +CREATE_SUBDIRS = NO + +# The OUTPUT_LANGUAGE tag is used to specify the language in which all +# documentation generated by doxygen is written. Doxygen will use this +# information to generate all constant output in the proper language. +# The default language is English, other supported languages are: +# Afrikaans, Arabic, Brazilian, Catalan, Chinese, Chinese-Traditional, +# Croatian, Czech, Danish, Dutch, Farsi, Finnish, French, German, Greek, +# Hungarian, Italian, Japanese, Japanese-en (Japanese with English messages), +# Korean, Korean-en, Lithuanian, Norwegian, Macedonian, Persian, Polish, +# Portuguese, Romanian, Russian, Serbian, Slovak, Slovene, Spanish, Swedish, +# and Ukrainian. + +OUTPUT_LANGUAGE = English + +# If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will +# include brief member descriptions after the members that are listed in +# the file and class documentation (similar to JavaDoc). +# Set to NO to disable this. + +BRIEF_MEMBER_DESC = YES + +# If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend +# the brief description of a member or function before the detailed description. +# Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the +# brief descriptions will be completely suppressed. + +REPEAT_BRIEF = YES + +# This tag implements a quasi-intelligent brief description abbreviator +# that is used to form the text in various listings. Each string +# in this list, if found as the leading text of the brief description, will be +# stripped from the text and the result after processing the whole list, is +# used as the annotated text. Otherwise, the brief description is used as-is. +# If left blank, the following values are used ("$name" is automatically +# replaced with the name of the entity): "The $name class" "The $name widget" +# "The $name file" "is" "provides" "specifies" "contains" +# "represents" "a" "an" "the" + +ABBREVIATE_BRIEF = + +# If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then +# Doxygen will generate a detailed section even if there is only a brief +# description. + +ALWAYS_DETAILED_SEC = NO + +# If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all +# inherited members of a class in the documentation of that class as if those +# members were ordinary class members. Constructors, destructors and assignment +# operators of the base classes will not be shown. + +INLINE_INHERITED_MEMB = NO + +# If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full +# path before files name in the file list and in the header files. If set +# to NO the shortest path that makes the file name unique will be used. + +FULL_PATH_NAMES = YES + +# If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag +# can be used to strip a user-defined part of the path. Stripping is +# only done if one of the specified strings matches the left-hand part of +# the path. The tag can be used to show relative paths in the file list. +# If left blank the directory from which doxygen is run is used as the +# path to strip. + +STRIP_FROM_PATH = + +# The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of +# the path mentioned in the documentation of a class, which tells +# the reader which header file to include in order to use a class. +# If left blank only the name of the header file containing the class +# definition is used. Otherwise one should specify the include paths that +# are normally passed to the compiler using the -I flag. + +STRIP_FROM_INC_PATH = + +# If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter +# (but less readable) file names. This can be useful is your file systems +# doesn't support long names like on DOS, Mac, or CD-ROM. + +SHORT_NAMES = NO + +# If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen +# will interpret the first line (until the first dot) of a JavaDoc-style +# comment as the brief description. If set to NO, the JavaDoc +# comments will behave just like regular Qt-style comments +# (thus requiring an explicit @brief command for a brief description.) + +JAVADOC_AUTOBRIEF = NO + +# If the QT_AUTOBRIEF tag is set to YES then Doxygen will +# interpret the first line (until the first dot) of a Qt-style +# comment as the brief description. If set to NO, the comments +# will behave just like regular Qt-style comments (thus requiring +# an explicit \brief command for a brief description.) + +QT_AUTOBRIEF = NO + +# The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen +# treat a multi-line C++ special comment block (i.e. a block of //! or /// +# comments) as a brief description. This used to be the default behaviour. +# The new default is to treat a multi-line C++ comment block as a detailed +# description. Set this tag to YES if you prefer the old behaviour instead. + +MULTILINE_CPP_IS_BRIEF = NO + +# If the DETAILS_AT_TOP tag is set to YES then Doxygen +# will output the detailed description near the top, like JavaDoc. +# If set to NO, the detailed description appears after the member +# documentation. + +DETAILS_AT_TOP = NO + +# If the INHERIT_DOCS tag is set to YES (the default) then an undocumented +# member inherits the documentation from any documented member that it +# re-implements. + +INHERIT_DOCS = YES + +# If the SEPARATE_MEMBER_PAGES tag is set to YES, then doxygen will produce +# a new page for each member. If set to NO, the documentation of a member will +# be part of the file/class/namespace that contains it. + +SEPARATE_MEMBER_PAGES = NO + +# The TAB_SIZE tag can be used to set the number of spaces in a tab. +# Doxygen uses this value to replace tabs by spaces in code fragments. + +TAB_SIZE = 2 + +# This tag can be used to specify a number of aliases that acts +# as commands in the documentation. An alias has the form "name=value". +# For example adding "sideeffect=\par Side Effects:\n" will allow you to +# put the command \sideeffect (or @sideeffect) in the documentation, which +# will result in a user-defined paragraph with heading "Side Effects:". +# You can put \n's in the value part of an alias to insert newlines. + +ALIASES = + +# Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C +# sources only. Doxygen will then generate output that is more tailored for C. +# For instance, some of the names that are used will be different. The list +# of all members will be omitted, etc. + +OPTIMIZE_OUTPUT_FOR_C = NO + +# Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java +# sources only. Doxygen will then generate output that is more tailored for +# Java. For instance, namespaces will be presented as packages, qualified +# scopes will look different, etc. + +OPTIMIZE_OUTPUT_JAVA = NO + +# Set the OPTIMIZE_FOR_FORTRAN tag to YES if your project consists of Fortran +# sources only. Doxygen will then generate output that is more tailored for +# Fortran. + +OPTIMIZE_FOR_FORTRAN = NO + +# Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL +# sources. Doxygen will then generate output that is tailored for +# VHDL. + +OPTIMIZE_OUTPUT_VHDL = NO + +# If you use STL classes (i.e. std::string, std::vector, etc.) but do not want +# to include (a tag file for) the STL sources as input, then you should +# set this tag to YES in order to let doxygen match functions declarations and +# definitions whose arguments contain STL classes (e.g. func(std::string); v.s. +# func(std::string) {}). This also make the inheritance and collaboration +# diagrams that involve STL classes more complete and accurate. + +BUILTIN_STL_SUPPORT = NO + +# If you use Microsoft's C++/CLI language, you should set this option to YES to +# enable parsing support. + +CPP_CLI_SUPPORT = NO + +# Set the SIP_SUPPORT tag to YES if your project consists of sip sources only. +# Doxygen will parse them like normal C++ but will assume all classes use public +# instead of private inheritance when no explicit protection keyword is present. + +SIP_SUPPORT = NO + +# For Microsoft's IDL there are propget and propput attributes to indicate getter +# and setter methods for a property. Setting this option to YES (the default) +# will make doxygen to replace the get and set methods by a property in the +# documentation. This will only work if the methods are indeed getting or +# setting a simple type. If this is not the case, or you want to show the +# methods anyway, you should set this option to NO. + +IDL_PROPERTY_SUPPORT = YES + +# If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC +# tag is set to YES, then doxygen will reuse the documentation of the first +# member in the group (if any) for the other members of the group. By default +# all members of a group must be documented explicitly. + +DISTRIBUTE_GROUP_DOC = NO + +# Set the SUBGROUPING tag to YES (the default) to allow class member groups of +# the same type (for instance a group of public functions) to be put as a +# subgroup of that type (e.g. under the Public Functions section). Set it to +# NO to prevent subgrouping. Alternatively, this can be done per class using +# the \nosubgrouping command. + +SUBGROUPING = YES + +# When TYPEDEF_HIDES_STRUCT is enabled, a typedef of a struct, union, or enum +# is documented as struct, union, or enum with the name of the typedef. So +# typedef struct TypeS {} TypeT, will appear in the documentation as a struct +# with name TypeT. When disabled the typedef will appear as a member of a file, +# namespace, or class. And the struct will be named TypeS. This can typically +# be useful for C code in case the coding convention dictates that all compound +# types are typedef'ed and only the typedef is referenced, never the tag name. + +TYPEDEF_HIDES_STRUCT = NO + +#--------------------------------------------------------------------------- +# Build related configuration options +#--------------------------------------------------------------------------- + +# If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in +# documentation are documented, even if no documentation was available. +# Private class members and static file members will be hidden unless +# the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES + +#EXTRACT_ALL = NO +EXTRACT_ALL = yes + +# If the EXTRACT_PRIVATE tag is set to YES all private members of a class +# will be included in the documentation. + +EXTRACT_PRIVATE = NO + +# If the EXTRACT_STATIC tag is set to YES all static members of a file +# will be included in the documentation. + +EXTRACT_STATIC = NO + +# If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs) +# defined locally in source files will be included in the documentation. +# If set to NO only classes defined in header files are included. + +EXTRACT_LOCAL_CLASSES = YES + +# This flag is only useful for Objective-C code. When set to YES local +# methods, which are defined in the implementation section but not in +# the interface are included in the documentation. +# If set to NO (the default) only methods in the interface are included. + +EXTRACT_LOCAL_METHODS = NO + +# If this flag is set to YES, the members of anonymous namespaces will be +# extracted and appear in the documentation as a namespace called +# 'anonymous_namespace{file}', where file will be replaced with the base +# name of the file that contains the anonymous namespace. By default +# anonymous namespace are hidden. + +EXTRACT_ANON_NSPACES = NO + +# If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all +# undocumented members of documented classes, files or namespaces. +# If set to NO (the default) these members will be included in the +# various overviews, but no documentation section is generated. +# This option has no effect if EXTRACT_ALL is enabled. + +HIDE_UNDOC_MEMBERS = NO + +# If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all +# undocumented classes that are normally visible in the class hierarchy. +# If set to NO (the default) these classes will be included in the various +# overviews. This option has no effect if EXTRACT_ALL is enabled. + +HIDE_UNDOC_CLASSES = NO + +# If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all +# friend (class|struct|union) declarations. +# If set to NO (the default) these declarations will be included in the +# documentation. + +HIDE_FRIEND_COMPOUNDS = NO + +# If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any +# documentation blocks found inside the body of a function. +# If set to NO (the default) these blocks will be appended to the +# function's detailed documentation block. + +HIDE_IN_BODY_DOCS = NO + +# The INTERNAL_DOCS tag determines if documentation +# that is typed after a \internal command is included. If the tag is set +# to NO (the default) then the documentation will be excluded. +# Set it to YES to include the internal documentation. + +INTERNAL_DOCS = NO + +# If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate +# file names in lower-case letters. If set to YES upper-case letters are also +# allowed. This is useful if you have classes or files whose names only differ +# in case and if your file system supports case sensitive file names. Windows +# and Mac users are advised to set this option to NO. + +CASE_SENSE_NAMES = YES + +# If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen +# will show members with their full class and namespace scopes in the +# documentation. If set to YES the scope will be hidden. + +HIDE_SCOPE_NAMES = NO + +# If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen +# will put a list of the files that are included by a file in the documentation +# of that file. + +SHOW_INCLUDE_FILES = YES + +# If the INLINE_INFO tag is set to YES (the default) then a tag [inline] +# is inserted in the documentation for inline members. + +INLINE_INFO = YES + +# If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen +# will sort the (detailed) documentation of file and class members +# alphabetically by member name. If set to NO the members will appear in +# declaration order. + +SORT_MEMBER_DOCS = YES + +# If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the +# brief documentation of file, namespace and class members alphabetically +# by member name. If set to NO (the default) the members will appear in +# declaration order. + +#SORT_BRIEF_DOCS = NO +SORT_BRIEF_DOCS = yes + +# If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the +# hierarchy of group names into alphabetical order. If set to NO (the default) +# the group names will appear in their defined order. + +SORT_GROUP_NAMES = NO + +# If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be +# sorted by fully-qualified names, including namespaces. If set to +# NO (the default), the class list will be sorted only by class name, +# not including the namespace part. +# Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES. +# Note: This option applies only to the class list, not to the +# alphabetical list. + +SORT_BY_SCOPE_NAME = NO + +# The GENERATE_TODOLIST tag can be used to enable (YES) or +# disable (NO) the todo list. This list is created by putting \todo +# commands in the documentation. + +GENERATE_TODOLIST = YES + +# The GENERATE_TESTLIST tag can be used to enable (YES) or +# disable (NO) the test list. This list is created by putting \test +# commands in the documentation. + +GENERATE_TESTLIST = YES + +# The GENERATE_BUGLIST tag can be used to enable (YES) or +# disable (NO) the bug list. This list is created by putting \bug +# commands in the documentation. + +GENERATE_BUGLIST = YES + +# The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or +# disable (NO) the deprecated list. This list is created by putting +# \deprecated commands in the documentation. + +GENERATE_DEPRECATEDLIST= YES + +# The ENABLED_SECTIONS tag can be used to enable conditional +# documentation sections, marked by \if sectionname ... \endif. + +ENABLED_SECTIONS = + +# The MAX_INITIALIZER_LINES tag determines the maximum number of lines +# the initial value of a variable or define consists of for it to appear in +# the documentation. If the initializer consists of more lines than specified +# here it will be hidden. Use a value of 0 to hide initializers completely. +# The appearance of the initializer of individual variables and defines in the +# documentation can be controlled using \showinitializer or \hideinitializer +# command in the documentation regardless of this setting. + +MAX_INITIALIZER_LINES = 30 + +# Set the SHOW_USED_FILES tag to NO to disable the list of files generated +# at the bottom of the documentation of classes and structs. If set to YES the +# list will mention the files that were used to generate the documentation. + +SHOW_USED_FILES = YES + +# If the sources in your project are distributed over multiple directories +# then setting the SHOW_DIRECTORIES tag to YES will show the directory hierarchy +# in the documentation. The default is NO. + +SHOW_DIRECTORIES = NO + +# Set the SHOW_FILES tag to NO to disable the generation of the Files page. +# This will remove the Files entry from the Quick Index and from the +# Folder Tree View (if specified). The default is YES. + +SHOW_FILES = YES + +# Set the SHOW_NAMESPACES tag to NO to disable the generation of the +# Namespaces page. This will remove the Namespaces entry from the Quick Index +# and from the Folder Tree View (if specified). The default is YES. + +SHOW_NAMESPACES = YES + +# The FILE_VERSION_FILTER tag can be used to specify a program or script that +# doxygen should invoke to get the current version for each file (typically from +# the version control system). Doxygen will invoke the program by executing (via +# popen()) the command , where is the value of +# the FILE_VERSION_FILTER tag, and is the name of an input file +# provided by doxygen. Whatever the program writes to standard output +# is used as the file version. See the manual for examples. + +FILE_VERSION_FILTER = + +#--------------------------------------------------------------------------- +# configuration options related to warning and progress messages +#--------------------------------------------------------------------------- + +# The QUIET tag can be used to turn on/off the messages that are generated +# by doxygen. Possible values are YES and NO. If left blank NO is used. + +QUIET = NO + +# The WARNINGS tag can be used to turn on/off the warning messages that are +# generated by doxygen. Possible values are YES and NO. If left blank +# NO is used. + +WARNINGS = YES + +# If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings +# for undocumented members. If EXTRACT_ALL is set to YES then this flag will +# automatically be disabled. + +WARN_IF_UNDOCUMENTED = YES + +# If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for +# potential errors in the documentation, such as not documenting some +# parameters in a documented function, or documenting parameters that +# don't exist or using markup commands wrongly. + +WARN_IF_DOC_ERROR = YES + +# This WARN_NO_PARAMDOC option can be abled to get warnings for +# functions that are documented, but have no documentation for their parameters +# or return value. If set to NO (the default) doxygen will only warn about +# wrong or incomplete parameter documentation, but not about the absence of +# documentation. + +WARN_NO_PARAMDOC = NO + +# The WARN_FORMAT tag determines the format of the warning messages that +# doxygen can produce. The string should contain the $file, $line, and $text +# tags, which will be replaced by the file and line number from which the +# warning originated and the warning text. Optionally the format may contain +# $version, which will be replaced by the version of the file (if it could +# be obtained via FILE_VERSION_FILTER) + +WARN_FORMAT = "$file:$line: $text" + +# The WARN_LOGFILE tag can be used to specify a file to which warning +# and error messages should be written. If left blank the output is written +# to stderr. + +WARN_LOGFILE = + +#--------------------------------------------------------------------------- +# configuration options related to the input files +#--------------------------------------------------------------------------- + +# The INPUT tag can be used to specify the files and/or directories that contain +# documented source files. You may enter file names like "myfile.cpp" or +# directories like "/usr/src/myproject". Separate the files or directories +# with spaces. + +INPUT = + +# This tag can be used to specify the character encoding of the source files +# that doxygen parses. Internally doxygen uses the UTF-8 encoding, which is +# also the default input encoding. Doxygen uses libiconv (or the iconv built +# into libc) for the transcoding. See http://www.gnu.org/software/libiconv for +# the list of possible encodings. + +INPUT_ENCODING = UTF-8 + +# If the value of the INPUT tag contains directories, you can use the +# FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp +# and *.h) to filter out the source-files in the directories. If left +# blank the following patterns are tested: +# *.c *.cc *.cxx *.cpp *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx +# *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm *.py *.f90 + +FILE_PATTERNS = *.lua + +# The RECURSIVE tag can be used to turn specify whether or not subdirectories +# should be searched for input files as well. Possible values are YES and NO. +# If left blank NO is used. + +RECURSIVE = NO + +# The EXCLUDE tag can be used to specify files and/or directories that should +# excluded from the INPUT source files. This way you can easily exclude a +# subdirectory from a directory tree whose root is specified with the INPUT tag. + +EXCLUDE = + +# The EXCLUDE_SYMLINKS tag can be used select whether or not files or +# directories that are symbolic links (a Unix filesystem feature) are excluded +# from the input. + +EXCLUDE_SYMLINKS = NO + +# If the value of the INPUT tag contains directories, you can use the +# EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude +# certain files from those directories. Note that the wildcards are matched +# against the file with absolute path, so to exclude all test directories +# for example use the pattern */test/* + +EXCLUDE_PATTERNS = + +# The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names +# (namespaces, classes, functions, etc.) that should be excluded from the +# output. The symbol name can be a fully qualified name, a word, or if the +# wildcard * is used, a substring. Examples: ANamespace, AClass, +# AClass::ANamespace, ANamespace::*Test + +EXCLUDE_SYMBOLS = + +# The EXAMPLE_PATH tag can be used to specify one or more files or +# directories that contain example code fragments that are included (see +# the \include command). + +EXAMPLE_PATH = + +# If the value of the EXAMPLE_PATH tag contains directories, you can use the +# EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp +# and *.h) to filter out the source-files in the directories. If left +# blank all files are included. + +EXAMPLE_PATTERNS = + +# If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be +# searched for input files to be used with the \include or \dontinclude +# commands irrespective of the value of the RECURSIVE tag. +# Possible values are YES and NO. If left blank NO is used. + +EXAMPLE_RECURSIVE = NO + +# The IMAGE_PATH tag can be used to specify one or more files or +# directories that contain image that are included in the documentation (see +# the \image command). + +IMAGE_PATH = + +# The INPUT_FILTER tag can be used to specify a program that doxygen should +# invoke to filter for each input file. Doxygen will invoke the filter program +# by executing (via popen()) the command , where +# is the value of the INPUT_FILTER tag, and is the name of an +# input file. Doxygen will then use the output that the filter program writes +# to standard output. If FILTER_PATTERNS is specified, this tag will be +# ignored. + +INPUT_FILTER = + +# The FILTER_PATTERNS tag can be used to specify filters on a per file pattern +# basis. Doxygen will compare the file name with each pattern and apply the +# filter if there is a match. The filters are a list of the form: +# pattern=filter (like *.cpp=my_cpp_filter). See INPUT_FILTER for further +# info on how filters are used. If FILTER_PATTERNS is empty, INPUT_FILTER +# is applied to all files. + +FILTER_PATTERNS = *.lua=lua2dox_filter + +# If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using +# INPUT_FILTER) will be used to filter the input files when producing source +# files to browse (i.e. when SOURCE_BROWSER is set to YES). + +FILTER_SOURCE_FILES = NO + +#--------------------------------------------------------------------------- +# configuration options related to source browsing +#--------------------------------------------------------------------------- + +# If the SOURCE_BROWSER tag is set to YES then a list of source files will +# be generated. Documented entities will be cross-referenced with these sources. +# Note: To get rid of all source code in the generated output, make sure also +# VERBATIM_HEADERS is set to NO. + +#SOURCE_BROWSER = NO +SOURCE_BROWSER = yes + +# Setting the INLINE_SOURCES tag to YES will include the body +# of functions and classes directly in the documentation. + +INLINE_SOURCES = NO + +# Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct +# doxygen to hide any special comment blocks from generated source code +# fragments. Normal C and C++ comments will always remain visible. + +STRIP_CODE_COMMENTS = YES + +# If the REFERENCED_BY_RELATION tag is set to YES +# then for each documented function all documented +# functions referencing it will be listed. + +REFERENCED_BY_RELATION = NO + +# If the REFERENCES_RELATION tag is set to YES +# then for each documented function all documented entities +# called/used by that function will be listed. + +REFERENCES_RELATION = NO + +# If the REFERENCES_LINK_SOURCE tag is set to YES (the default) +# and SOURCE_BROWSER tag is set to YES, then the hyperlinks from +# functions in REFERENCES_RELATION and REFERENCED_BY_RELATION lists will +# link to the source code. Otherwise they will link to the documentstion. + +REFERENCES_LINK_SOURCE = YES + +# If the USE_HTAGS tag is set to YES then the references to source code +# will point to the HTML generated by the htags(1) tool instead of doxygen +# built-in source browser. The htags tool is part of GNU's global source +# tagging system (see http://www.gnu.org/software/global/global.html). You +# will need version 4.8.6 or higher. + +USE_HTAGS = NO + +# If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen +# will generate a verbatim copy of the header file for each class for +# which an include is specified. Set to NO to disable this. + +VERBATIM_HEADERS = YES + +#--------------------------------------------------------------------------- +# configuration options related to the alphabetical class index +#--------------------------------------------------------------------------- + +# If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index +# of all compounds will be generated. Enable this if the project +# contains a lot of classes, structs, unions or interfaces. + +ALPHABETICAL_INDEX = NO + +# If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then +# the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns +# in which this list will be split (can be a number in the range [1..20]) + +COLS_IN_ALPHA_INDEX = 5 + +# In case all classes in a project start with a common prefix, all +# classes will be put under the same header in the alphabetical index. +# The IGNORE_PREFIX tag can be used to specify one or more prefixes that +# should be ignored while generating the index headers. + +IGNORE_PREFIX = + +#--------------------------------------------------------------------------- +# configuration options related to the HTML output +#--------------------------------------------------------------------------- + +# If the GENERATE_HTML tag is set to YES (the default) Doxygen will +# generate HTML output. + +GENERATE_HTML = YES + +# The HTML_OUTPUT tag is used to specify where the HTML docs will be put. +# If a relative path is entered the value of OUTPUT_DIRECTORY will be +# put in front of it. If left blank `html' will be used as the default path. + +HTML_OUTPUT = html + +# The HTML_FILE_EXTENSION tag can be used to specify the file extension for +# each generated HTML page (for example: .htm,.php,.asp). If it is left blank +# doxygen will generate files with .html extension. + +HTML_FILE_EXTENSION = .html + +# The HTML_HEADER tag can be used to specify a personal HTML header for +# each generated HTML page. If it is left blank doxygen will generate a +# standard header. + +HTML_HEADER = + +# The HTML_FOOTER tag can be used to specify a personal HTML footer for +# each generated HTML page. If it is left blank doxygen will generate a +# standard footer. + +HTML_FOOTER = + +# The HTML_STYLESHEET tag can be used to specify a user-defined cascading +# style sheet that is used by each HTML page. It can be used to +# fine-tune the look of the HTML output. If the tag is left blank doxygen +# will generate a default style sheet. Note that doxygen will try to copy +# the style sheet file to the HTML output directory, so don't put your own +# stylesheet in the HTML output directory as well, or it will be erased! + +HTML_STYLESHEET = + +# If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes, +# files or namespaces will be aligned in HTML using tables. If set to +# NO a bullet list will be used. + +HTML_ALIGN_MEMBERS = YES + +# If the GENERATE_HTMLHELP tag is set to YES, additional index files +# will be generated that can be used as input for tools like the +# Microsoft HTML help workshop to generate a compiled HTML help file (.chm) +# of the generated HTML documentation. + +GENERATE_HTMLHELP = NO + +# If the GENERATE_DOCSET tag is set to YES, additional index files +# will be generated that can be used as input for Apple's Xcode 3 +# integrated development environment, introduced with OSX 10.5 (Leopard). +# To create a documentation set, doxygen will generate a Makefile in the +# HTML output directory. Running make will produce the docset in that +# directory and running "make install" will install the docset in +# ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find +# it at startup. + +GENERATE_DOCSET = NO + +# When GENERATE_DOCSET tag is set to YES, this tag determines the name of the +# feed. A documentation feed provides an umbrella under which multiple +# documentation sets from a single provider (such as a company or product suite) +# can be grouped. + +DOCSET_FEEDNAME = "Doxygen generated docs" + +# When GENERATE_DOCSET tag is set to YES, this tag specifies a string that +# should uniquely identify the documentation set bundle. This should be a +# reverse domain-name style string, e.g. com.mycompany.MyDocSet. Doxygen +# will append .docset to the name. + +DOCSET_BUNDLE_ID = org.doxygen.Project + +# If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML +# documentation will contain sections that can be hidden and shown after the +# page has loaded. For this to work a browser that supports +# JavaScript and DHTML is required (for instance Mozilla 1.0+, Firefox +# Netscape 6.0+, Internet explorer 5.0+, Konqueror, or Safari). + +HTML_DYNAMIC_SECTIONS = NO + +# If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can +# be used to specify the file name of the resulting .chm file. You +# can add a path in front of the file if the result should not be +# written to the html output directory. + +CHM_FILE = + +# If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can +# be used to specify the location (absolute path including file name) of +# the HTML help compiler (hhc.exe). If non-empty doxygen will try to run +# the HTML help compiler on the generated index.hhp. + +HHC_LOCATION = + +# If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag +# controls if a separate .chi index file is generated (YES) or that +# it should be included in the master .chm file (NO). + +GENERATE_CHI = NO + +# If the GENERATE_HTMLHELP tag is set to YES, the CHM_INDEX_ENCODING +# is used to encode HtmlHelp index (hhk), content (hhc) and project file +# content. + +CHM_INDEX_ENCODING = + +# If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag +# controls whether a binary table of contents is generated (YES) or a +# normal table of contents (NO) in the .chm file. + +BINARY_TOC = NO + +# The TOC_EXPAND flag can be set to YES to add extra items for group members +# to the contents of the HTML help documentation and to the tree view. + +TOC_EXPAND = NO + +# The DISABLE_INDEX tag can be used to turn on/off the condensed index at +# top of each HTML page. The value NO (the default) enables the index and +# the value YES disables it. + +DISABLE_INDEX = NO + +# This tag can be used to set the number of enum values (range [1..20]) +# that doxygen will group on one line in the generated HTML documentation. + +ENUM_VALUES_PER_LINE = 4 + +# The GENERATE_TREEVIEW tag is used to specify whether a tree-like index +# structure should be generated to display hierarchical information. +# If the tag value is set to FRAME, a side panel will be generated +# containing a tree-like index structure (just like the one that +# is generated for HTML Help). For this to work a browser that supports +# JavaScript, DHTML, CSS and frames is required (for instance Mozilla 1.0+, +# Netscape 6.0+, Internet explorer 5.0+, or Konqueror). Windows users are +# probably better off using the HTML help feature. Other possible values +# for this tag are: HIERARCHIES, which will generate the Groups, Directories, +# and Class Hiererachy pages using a tree view instead of an ordered list; +# ALL, which combines the behavior of FRAME and HIERARCHIES; and NONE, which +# disables this behavior completely. For backwards compatibility with previous +# releases of Doxygen, the values YES and NO are equivalent to FRAME and NONE +# respectively. + +GENERATE_TREEVIEW = NONE + +# If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be +# used to set the initial width (in pixels) of the frame in which the tree +# is shown. + +TREEVIEW_WIDTH = 250 + +# Use this tag to change the font size of Latex formulas included +# as images in the HTML documentation. The default is 10. Note that +# when you change the font size after a successful doxygen run you need +# to manually remove any form_*.png images from the HTML output directory +# to force them to be regenerated. + +FORMULA_FONTSIZE = 10 + +#--------------------------------------------------------------------------- +# configuration options related to the LaTeX output +#--------------------------------------------------------------------------- + +# If the GENERATE_LATEX tag is set to YES (the default) Doxygen will +# generate Latex output. + +#GENERATE_LATEX = YES +GENERATE_LATEX = no + +# The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put. +# If a relative path is entered the value of OUTPUT_DIRECTORY will be +# put in front of it. If left blank `latex' will be used as the default path. + +LATEX_OUTPUT = latex + +# The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be +# invoked. If left blank `latex' will be used as the default command name. + +LATEX_CMD_NAME = latex + +# The MAKEINDEX_CMD_NAME tag can be used to specify the command name to +# generate index for LaTeX. If left blank `makeindex' will be used as the +# default command name. + +MAKEINDEX_CMD_NAME = makeindex + +# If the COMPACT_LATEX tag is set to YES Doxygen generates more compact +# LaTeX documents. This may be useful for small projects and may help to +# save some trees in general. + +COMPACT_LATEX = NO + +# The PAPER_TYPE tag can be used to set the paper type that is used +# by the printer. Possible values are: a4, a4wide, letter, legal and +# executive. If left blank a4wide will be used. + +PAPER_TYPE = a4wide + +# The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX +# packages that should be included in the LaTeX output. + +EXTRA_PACKAGES = + +# The LATEX_HEADER tag can be used to specify a personal LaTeX header for +# the generated latex document. The header should contain everything until +# the first chapter. If it is left blank doxygen will generate a +# standard header. Notice: only use this tag if you know what you are doing! + +LATEX_HEADER = + +# If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated +# is prepared for conversion to pdf (using ps2pdf). The pdf file will +# contain links (just like the HTML output) instead of page references +# This makes the output suitable for online browsing using a pdf viewer. + +PDF_HYPERLINKS = YES + +# If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of +# plain latex in the generated Makefile. Set this option to YES to get a +# higher quality PDF documentation. + +USE_PDFLATEX = YES + +# If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode. +# command to the generated LaTeX files. This will instruct LaTeX to keep +# running if errors occur, instead of asking the user for help. +# This option is also used when generating formulas in HTML. + +LATEX_BATCHMODE = NO + +# If LATEX_HIDE_INDICES is set to YES then doxygen will not +# include the index chapters (such as File Index, Compound Index, etc.) +# in the output. + +LATEX_HIDE_INDICES = NO + +#--------------------------------------------------------------------------- +# configuration options related to the RTF output +#--------------------------------------------------------------------------- + +# If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output +# The RTF output is optimized for Word 97 and may not look very pretty with +# other RTF readers or editors. + +GENERATE_RTF = NO + +# The RTF_OUTPUT tag is used to specify where the RTF docs will be put. +# If a relative path is entered the value of OUTPUT_DIRECTORY will be +# put in front of it. If left blank `rtf' will be used as the default path. + +RTF_OUTPUT = rtf + +# If the COMPACT_RTF tag is set to YES Doxygen generates more compact +# RTF documents. This may be useful for small projects and may help to +# save some trees in general. + +COMPACT_RTF = NO + +# If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated +# will contain hyperlink fields. The RTF file will +# contain links (just like the HTML output) instead of page references. +# This makes the output suitable for online browsing using WORD or other +# programs which support those fields. +# Note: wordpad (write) and others do not support links. + +RTF_HYPERLINKS = NO + +# Load stylesheet definitions from file. Syntax is similar to doxygen's +# config file, i.e. a series of assignments. You only have to provide +# replacements, missing definitions are set to their default value. + +RTF_STYLESHEET_FILE = + +# Set optional variables used in the generation of an rtf document. +# Syntax is similar to doxygen's config file. + +RTF_EXTENSIONS_FILE = + +#--------------------------------------------------------------------------- +# configuration options related to the man page output +#--------------------------------------------------------------------------- + +# If the GENERATE_MAN tag is set to YES (the default) Doxygen will +# generate man pages + +GENERATE_MAN = NO + +# The MAN_OUTPUT tag is used to specify where the man pages will be put. +# If a relative path is entered the value of OUTPUT_DIRECTORY will be +# put in front of it. If left blank `man' will be used as the default path. + +MAN_OUTPUT = man + +# The MAN_EXTENSION tag determines the extension that is added to +# the generated man pages (default is the subroutine's section .3) + +MAN_EXTENSION = .3 + +# If the MAN_LINKS tag is set to YES and Doxygen generates man output, +# then it will generate one additional man file for each entity +# documented in the real man page(s). These additional files +# only source the real man page, but without them the man command +# would be unable to find the correct page. The default is NO. + +MAN_LINKS = NO + +#--------------------------------------------------------------------------- +# configuration options related to the XML output +#--------------------------------------------------------------------------- + +# If the GENERATE_XML tag is set to YES Doxygen will +# generate an XML file that captures the structure of +# the code including all documentation. + +GENERATE_XML = NO + +# The XML_OUTPUT tag is used to specify where the XML pages will be put. +# If a relative path is entered the value of OUTPUT_DIRECTORY will be +# put in front of it. If left blank `xml' will be used as the default path. + +XML_OUTPUT = xml + +# The XML_SCHEMA tag can be used to specify an XML schema, +# which can be used by a validating XML parser to check the +# syntax of the XML files. + +XML_SCHEMA = + +# The XML_DTD tag can be used to specify an XML DTD, +# which can be used by a validating XML parser to check the +# syntax of the XML files. + +XML_DTD = + +# If the XML_PROGRAMLISTING tag is set to YES Doxygen will +# dump the program listings (including syntax highlighting +# and cross-referencing information) to the XML output. Note that +# enabling this will significantly increase the size of the XML output. + +XML_PROGRAMLISTING = YES + +#--------------------------------------------------------------------------- +# configuration options for the AutoGen Definitions output +#--------------------------------------------------------------------------- + +# If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will +# generate an AutoGen Definitions (see autogen.sf.net) file +# that captures the structure of the code including all +# documentation. Note that this feature is still experimental +# and incomplete at the moment. + +GENERATE_AUTOGEN_DEF = NO + +#--------------------------------------------------------------------------- +# configuration options related to the Perl module output +#--------------------------------------------------------------------------- + +# If the GENERATE_PERLMOD tag is set to YES Doxygen will +# generate a Perl module file that captures the structure of +# the code including all documentation. Note that this +# feature is still experimental and incomplete at the +# moment. + +GENERATE_PERLMOD = NO + +# If the PERLMOD_LATEX tag is set to YES Doxygen will generate +# the necessary Makefile rules, Perl scripts and LaTeX code to be able +# to generate PDF and DVI output from the Perl module output. + +PERLMOD_LATEX = NO + +# If the PERLMOD_PRETTY tag is set to YES the Perl module output will be +# nicely formatted so it can be parsed by a human reader. This is useful +# if you want to understand what is going on. On the other hand, if this +# tag is set to NO the size of the Perl module output will be much smaller +# and Perl will parse it just the same. + +PERLMOD_PRETTY = YES + +# The names of the make variables in the generated doxyrules.make file +# are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX. +# This is useful so different doxyrules.make files included by the same +# Makefile don't overwrite each other's variables. + +PERLMOD_MAKEVAR_PREFIX = + +#--------------------------------------------------------------------------- +# Configuration options related to the preprocessor +#--------------------------------------------------------------------------- + +# If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will +# evaluate all C-preprocessor directives found in the sources and include +# files. + +ENABLE_PREPROCESSING = YES + +# If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro +# names in the source code. If set to NO (the default) only conditional +# compilation will be performed. Macro expansion can be done in a controlled +# way by setting EXPAND_ONLY_PREDEF to YES. + +MACRO_EXPANSION = NO + +# If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES +# then the macro expansion is limited to the macros specified with the +# PREDEFINED and EXPAND_AS_DEFINED tags. + +EXPAND_ONLY_PREDEF = NO + +# If the SEARCH_INCLUDES tag is set to YES (the default) the includes files +# in the INCLUDE_PATH (see below) will be search if a #include is found. + +SEARCH_INCLUDES = YES + +# The INCLUDE_PATH tag can be used to specify one or more directories that +# contain include files that are not input files but should be processed by +# the preprocessor. + +INCLUDE_PATH = + +# You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard +# patterns (like *.h and *.hpp) to filter out the header-files in the +# directories. If left blank, the patterns specified with FILE_PATTERNS will +# be used. + +INCLUDE_FILE_PATTERNS = + +# The PREDEFINED tag can be used to specify one or more macro names that +# are defined before the preprocessor is started (similar to the -D option of +# gcc). The argument of the tag is a list of macros of the form: name +# or name=definition (no spaces). If the definition and the = are +# omitted =1 is assumed. To prevent a macro definition from being +# undefined via #undef or recursively expanded use the := operator +# instead of the = operator. + +PREDEFINED = + +# If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then +# this tag can be used to specify a list of macro names that should be expanded. +# The macro definition that is found in the sources will be used. +# Use the PREDEFINED tag if you want to use a different macro definition. + +EXPAND_AS_DEFINED = + +# If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then +# doxygen's preprocessor will remove all function-like macros that are alone +# on a line, have an all uppercase name, and do not end with a semicolon. Such +# function macros are typically used for boiler-plate code, and will confuse +# the parser if not removed. + +SKIP_FUNCTION_MACROS = YES + +#--------------------------------------------------------------------------- +# Configuration::additions related to external references +#--------------------------------------------------------------------------- + +# The TAGFILES option can be used to specify one or more tagfiles. +# Optionally an initial location of the external documentation +# can be added for each tagfile. The format of a tag file without +# this location is as follows: +# TAGFILES = file1 file2 ... +# Adding location for the tag files is done as follows: +# TAGFILES = file1=loc1 "file2 = loc2" ... +# where "loc1" and "loc2" can be relative or absolute paths or +# URLs. If a location is present for each tag, the installdox tool +# does not have to be run to correct the links. +# Note that each tag file must have a unique name +# (where the name does NOT include the path) +# If a tag file is not located in the directory in which doxygen +# is run, you must also specify the path to the tagfile here. + +TAGFILES = + +# When a file name is specified after GENERATE_TAGFILE, doxygen will create +# a tag file that is based on the input files it reads. + +GENERATE_TAGFILE = + +# If the ALLEXTERNALS tag is set to YES all external classes will be listed +# in the class index. If set to NO only the inherited external classes +# will be listed. + +ALLEXTERNALS = NO + +# If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed +# in the modules index. If set to NO, only the current project's groups will +# be listed. + +EXTERNAL_GROUPS = YES + +# The PERL_PATH should be the absolute path and name of the perl script +# interpreter (i.e. the result of `which perl'). + +PERL_PATH = /usr/bin/perl + +#--------------------------------------------------------------------------- +# Configuration options related to the dot tool +#--------------------------------------------------------------------------- + +# If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will +# generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base +# or super classes. Setting the tag to NO turns the diagrams off. Note that +# this option is superseded by the HAVE_DOT option below. This is only a +# fallback. It is recommended to install and use dot, since it yields more +# powerful graphs. + +CLASS_DIAGRAMS = YES + +# You can define message sequence charts within doxygen comments using the \msc +# command. Doxygen will then run the mscgen tool (see +# http://www.mcternan.me.uk/mscgen/) to produce the chart and insert it in the +# documentation. The MSCGEN_PATH tag allows you to specify the directory where +# the mscgen tool resides. If left empty the tool is assumed to be found in the +# default search path. + +MSCGEN_PATH = + +# If set to YES, the inheritance and collaboration graphs will hide +# inheritance and usage relations if the target is undocumented +# or is not a class. + +HIDE_UNDOC_RELATIONS = YES + +# If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is +# available from the path. This tool is part of Graphviz, a graph visualization +# toolkit from AT&T and Lucent Bell Labs. The other options in this section +# have no effect if this option is set to NO (the default) + +HAVE_DOT = NO + +# By default doxygen will write a font called FreeSans.ttf to the output +# directory and reference it in all dot files that doxygen generates. This +# font does not include all possible unicode characters however, so when you need +# these (or just want a differently looking font) you can specify the font name +# using DOT_FONTNAME. You need need to make sure dot is able to find the font, +# which can be done by putting it in a standard location or by setting the +# DOTFONTPATH environment variable or by setting DOT_FONTPATH to the directory +# containing the font. + +DOT_FONTNAME = FreeSans + +# By default doxygen will tell dot to use the output directory to look for the +# FreeSans.ttf font (which doxygen will put there itself). If you specify a +# different font using DOT_FONTNAME you can set the path where dot +# can find it using this tag. + +DOT_FONTPATH = + +# If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen +# will generate a graph for each documented class showing the direct and +# indirect inheritance relations. Setting this tag to YES will force the +# the CLASS_DIAGRAMS tag to NO. + +CLASS_GRAPH = YES + +# If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen +# will generate a graph for each documented class showing the direct and +# indirect implementation dependencies (inheritance, containment, and +# class references variables) of the class with other documented classes. + +COLLABORATION_GRAPH = YES + +# If the GROUP_GRAPHS and HAVE_DOT tags are set to YES then doxygen +# will generate a graph for groups, showing the direct groups dependencies + +GROUP_GRAPHS = YES + +# If the UML_LOOK tag is set to YES doxygen will generate inheritance and +# collaboration diagrams in a style similar to the OMG's Unified Modeling +# Language. + +UML_LOOK = NO + +# If set to YES, the inheritance and collaboration graphs will show the +# relations between templates and their instances. + +TEMPLATE_RELATIONS = NO + +# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT +# tags are set to YES then doxygen will generate a graph for each documented +# file showing the direct and indirect include dependencies of the file with +# other documented files. + +INCLUDE_GRAPH = YES + +# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and +# HAVE_DOT tags are set to YES then doxygen will generate a graph for each +# documented header file showing the documented files that directly or +# indirectly include this file. + +INCLUDED_BY_GRAPH = YES + +# If the CALL_GRAPH and HAVE_DOT options are set to YES then +# doxygen will generate a call dependency graph for every global function +# or class method. Note that enabling this option will significantly increase +# the time of a run. So in most cases it will be better to enable call graphs +# for selected functions only using the \callgraph command. + +CALL_GRAPH = NO + +# If the CALLER_GRAPH and HAVE_DOT tags are set to YES then +# doxygen will generate a caller dependency graph for every global function +# or class method. Note that enabling this option will significantly increase +# the time of a run. So in most cases it will be better to enable caller +# graphs for selected functions only using the \callergraph command. + +CALLER_GRAPH = NO + +# If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen +# will graphical hierarchy of all classes instead of a textual one. + +GRAPHICAL_HIERARCHY = YES + +# If the DIRECTORY_GRAPH, SHOW_DIRECTORIES and HAVE_DOT tags are set to YES +# then doxygen will show the dependencies a directory has on other directories +# in a graphical way. The dependency relations are determined by the #include +# relations between the files in the directories. + +DIRECTORY_GRAPH = YES + +# The DOT_IMAGE_FORMAT tag can be used to set the image format of the images +# generated by dot. Possible values are png, jpg, or gif +# If left blank png will be used. + +DOT_IMAGE_FORMAT = png + +# The tag DOT_PATH can be used to specify the path where the dot tool can be +# found. If left blank, it is assumed the dot tool can be found in the path. + +DOT_PATH = + +# The DOTFILE_DIRS tag can be used to specify one or more directories that +# contain dot files that are included in the documentation (see the +# \dotfile command). + +DOTFILE_DIRS = + +# The DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of +# nodes that will be shown in the graph. If the number of nodes in a graph +# becomes larger than this value, doxygen will truncate the graph, which is +# visualized by representing a node as a red box. Note that doxygen if the +# number of direct children of the root node in a graph is already larger than +# DOT_GRAPH_MAX_NODES then the graph will not be shown at all. Also note +# that the size of a graph can be further restricted by MAX_DOT_GRAPH_DEPTH. + +DOT_GRAPH_MAX_NODES = 50 + +# The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the +# graphs generated by dot. A depth value of 3 means that only nodes reachable +# from the root by following a path via at most 3 edges will be shown. Nodes +# that lay further from the root node will be omitted. Note that setting this +# option to 1 or 2 may greatly reduce the computation time needed for large +# code bases. Also note that the size of a graph can be further restricted by +# DOT_GRAPH_MAX_NODES. Using a depth of 0 means no depth restriction. + +MAX_DOT_GRAPH_DEPTH = 0 + +# Set the DOT_TRANSPARENT tag to YES to generate images with a transparent +# background. This is enabled by default, which results in a transparent +# background. Warning: Depending on the platform used, enabling this option +# may lead to badly anti-aliased labels on the edges of a graph (i.e. they +# become hard to read). + +DOT_TRANSPARENT = YES + +# Set the DOT_MULTI_TARGETS tag to YES allow dot to generate multiple output +# files in one run (i.e. multiple -o and -T options on the command line). This +# makes dot run faster, but since only newer versions of dot (>1.8.10) +# support this, this feature is disabled by default. + +DOT_MULTI_TARGETS = NO + +# If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will +# generate a legend page explaining the meaning of the various boxes and +# arrows in the dot generated graphs. + +GENERATE_LEGEND = YES + +# If the DOT_CLEANUP tag is set to YES (the default) Doxygen will +# remove the intermediate dot files that are used to generate +# the various graphs. + +DOT_CLEANUP = YES + +#--------------------------------------------------------------------------- +# Configuration::additions related to the search engine +#--------------------------------------------------------------------------- + +# The SEARCHENGINE tag specifies whether or not a search engine should be +# used. If set to NO the values of all tags below this one will be ignored. + +SEARCHENGINE = NO diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/lua/animals.lua b/Master/texmf-dist/doc/support/lua2dox/examples/lua/animals.lua new file mode 100644 index 00000000000..4816cd0d4b9 --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/examples/lua/animals.lua @@ -0,0 +1,120 @@ +---- Copyright 2012 Simon Dales +-- +-- This work may be distributed and/or modified under the +-- conditions of the LaTeX Project Public License, either version 1.3 +-- of this license or (at your option) any later version. +-- The latest version of this license is in +-- http://www.latex-project.org/lppl.txt +-- +-- This work has the LPPL maintenance status `maintained'. +-- +-- The Current Maintainer of this work is Simon Dales. +-- + +--[[! + \file + \brief test some classes + + ]] + +require 'class' + +--! \brief write to stdout +function TIO_write(Str) + if Str then + io.write(Str) + end +end + +--! \brief writeln to stdout +function TIO_writeln(Str) + if Str then + io.write(Str) + end + io.write('\n') +end + +--! \class Animal +--! \brief a base class +Animal = class() + +--! \brief constructor +function Animal.init(this) + this:setKind('animal') +end + +--! \brief set kind of object +function Animal.setKind(this,Kind) + this.kind = Kind +end + +--! \brief say the call of this animal +function Animal.call(this) + local speigel = this.speigel + if speigel then + speigel = ' says "' .. speigel .. '"' + else + speigel = ' ' + end + + TIO_writeln(this.kind .. speigel) +end + +--! \brief an abstract bird +Bird = class(Animal) + +--! \brief constructor +function Bird.init(this) + Animal.init(this) + this:setKind('bird') +end + +--! \brief a subclassed bird +Pigeon = class(Bird) + +--! \brief constructor +function Pigeon.init(this) + Bird.init(this) + this:setKind('pigeon') + this.speigel = 'oh my poor toe Betty' +end + +--! \brief another subclassed bird +RedKite = class(Bird) + +--! \brief constructor +function RedKite.init(this) + Bird.init(this) + this:setKind('red kite') + this.speigel = 'weee-ooo ee oo ee oo ee oo' +end + +--! \brief a base mammal +Mammal = class(Animal) + +--! \brief constructor +function Mammal.init(this) + Animal.init(this) +end + +--! \brief a subclassed mammal +Cat = class(Mammal) + +--! \brief constructor +function Cat.init(this) + Mammal.init(this) + this:setKind('cat') + this.speigel = 'meow' +end + +--! \brief another subclassed mammal +Dog = class(Mammal) + +--! \brief constructor +function Dog.init(this) + Mammal.init(this) + this:setKind('dog') + this.speigel = 'woof' +end + +--eof \ No newline at end of file diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/lua/class.lua b/Master/texmf-dist/doc/support/lua2dox/examples/lua/class.lua new file mode 100644 index 00000000000..7e155ceb050 --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/examples/lua/class.lua @@ -0,0 +1,85 @@ +---- Copyright 2011 Simon Dales +-- +-- This work may be distributed and/or modified under the +-- conditions of the LaTeX Project Public License, either version 1.3 +-- of this license or (at your option) any later version. +-- The latest version of this license is in +-- http://www.latex-project.org/lppl.txt +-- +-- This work has the LPPL maintenance status `maintained'. +-- +-- The Current Maintainer of this work is Simon Dales. +-- + +--[[! + \file + \brief enables classes in lua + ]] + +--[[ class.lua +-- Compatible with Lua 5.1 (not 5.0). + + --------------------- + + ]]-- +--! \brief ``declare'' as class +--! +--! use as: +--! \code{lua} +--! TWibble = class() +--! function TWibble:init(instance) +--! self.instance = instance +--! -- more stuff here +--! end +--! \endcode +--! +function class(BaseClass, ClassInitialiser) + local newClass = {} -- a new class newClass + if not ClassInitialiser and type(BaseClass) == 'function' then + ClassInitialiser = BaseClass + BaseClass = nil + elseif type(BaseClass) == 'table' then + -- our new class is a shallow copy of the base class! + for i,v in pairs(BaseClass) do + newClass[i] = v + end + newClass._base = BaseClass + end + -- the class will be the metatable for all its newInstanceects, + -- and they will look up their methods in it. + newClass.__index = newClass + + -- expose a constructor which can be called by () + local classMetatable = {} + classMetatable.__call = + function(class_tbl, ...) + local newInstance = {} + setmetatable(newInstance,newClass) + --if init then + -- init(newInstance,...) + if class_tbl.init then + class_tbl.init(newInstance,...) + else + -- make sure that any stuff from the base class is initialized! + if BaseClass and BaseClass.init then + BaseClass.init(newInstance, ...) + end + end + return newInstance + end + newClass.init = ClassInitialiser + newClass.is_a = + function(this, klass) + local thisMetabable = getmetatable(this) + while thisMetabable do + if thisMetabable == klass then + return true + end + thisMetabable = thisMetabable._base + end + return false + end + setmetatable(newClass, classMetatable) + return newClass +end +--eof \ No newline at end of file diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/animals_8lua-source.html b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/animals_8lua-source.html new file mode 100644 index 00000000000..ef52b3662e6 --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/animals_8lua-source.html @@ -0,0 +1,141 @@ + + +Sample Code: animals.lua Source File + + + + + +
Generated on Mon Jun 11 16:15:30 2012 for Sample Code by  + +doxygen 1.5.6
+ + diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/animals_8lua.html b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/animals_8lua.html new file mode 100644 index 00000000000..deefb5e17a5 --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/animals_8lua.html @@ -0,0 +1,113 @@ + + +Sample Code: animals.lua File Reference + + + + + +
+

animals.lua File Reference

test some classes More... +

+ +

+Go to the source code of this file. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

Classes

class  Animal
 a base class More...
class  Bird
 an abstract bird More...
class  Cat
 a subclassed mammal More...
class  Dog
 another subclassed mammal More...
class  Mammal
 a base mammal More...
class  Pigeon
 a subclassed bird More...
class  RedKite
 another subclassed bird More...

Functions

function TIO_write (Str)
 write to stdout
function TIO_writeln (Str)
 writeln to stdout
+


Detailed Description

+test some classes +

+ +

Definition in file animals.lua.

+

Function Documentation

+ +
+
+ + + + + + + + + +
function TIO_write (Str   ) 
+
+
+ +

+write to stdout +

+ +

Definition at line 23 of file animals.lua.

+ +
+

+ +

+
+ + + + + + + + + +
function TIO_writeln (Str   ) 
+
+
+ +

+writeln to stdout +

+ +

Definition at line 30 of file animals.lua.

+ +
+

+

+
Generated on Mon Jun 11 16:15:30 2012 for Sample Code by  + +doxygen 1.5.6
+ + diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/annotated.html b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/annotated.html new file mode 100644 index 00000000000..562b4c6971b --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/annotated.html @@ -0,0 +1,39 @@ + + +Sample Code: Class List + + + + + +
+

Class List

Here are the classes, structs, unions and interfaces with brief descriptions: + + + + + + + +
AnimalBase class
BirdAbstract bird
CatSubclassed mammal
DogAnother subclassed mammal
MammalBase mammal
PigeonSubclassed bird
RedKiteAnother subclassed bird
+
+
Generated on Mon Jun 11 16:15:30 2012 for Sample Code by  + +doxygen 1.5.6
+ + diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classAnimal-members.html b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classAnimal-members.html new file mode 100644 index 00000000000..1eb543d4790 --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classAnimal-members.html @@ -0,0 +1,34 @@ + + +Sample Code: Member List + + + + + +
+

Animal Member List

This is the complete list of members for Animal, including all inherited members.

+ + + +
call(this)Animal
init(this)Animal
setKind(this, Kind)Animal

+
Generated on Mon Jun 11 16:15:30 2012 for Sample Code by  + +doxygen 1.5.6
+ + diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classAnimal.html b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classAnimal.html new file mode 100644 index 00000000000..fcf3276c14c --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classAnimal.html @@ -0,0 +1,151 @@ + + +Sample Code: Animal Class Reference + + + + + +
+

Animal Class Reference

a base class +More... +

+

+Inheritance diagram for Animal:
+
+ +

+ +Bird +Mammal +Pigeon +RedKite +Cat +Dog + +
+ +

+List of all members. + + + + + + + + + + + +

Public Member Functions

 call (this)
 say the call of this animal
 init (this)
 constructor
 setKind (this, Kind)
 set kind of object
+


Detailed Description

+a base class +

Definition at line 39 of file animals.lua.

+

Member Function Documentation

+ +
+
+ + + + + + + + + +
Animal::call (this   ) 
+
+
+ +

+say the call of this animal +

+ +

Definition at line 52 of file animals.lua.

+ +
+

+ +

+
+ + + + + + + + + +
Animal::init (this   ) 
+
+
+ +

+constructor +

+ +

Reimplemented in Bird, Pigeon, RedKite, Mammal, Cat, and Dog.

+ +

Definition at line 42 of file animals.lua.

+ +
+

+ +

+
+ + + + + + + + + + + + + + + + + + +
Animal::setKind (this ,
Kind  
)
+
+
+ +

+set kind of object +

+ +

Definition at line 47 of file animals.lua.

+ +
+

+


The documentation for this class was generated from the following file: +
+
Generated on Mon Jun 11 16:15:30 2012 for Sample Code by  + +doxygen 1.5.6
+ + diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classAnimal.png b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classAnimal.png new file mode 100644 index 00000000000..796bc999ca1 Binary files /dev/null and b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classAnimal.png differ diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classBird-members.html b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classBird-members.html new file mode 100644 index 00000000000..acb22e7c62f --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classBird-members.html @@ -0,0 +1,34 @@ + + +Sample Code: Member List + + + + + +
+

Bird Member List

This is the complete list of members for Bird, including all inherited members.

+ + + +
call(this)Animal
init(this)Bird
setKind(this, Kind)Animal

+
Generated on Mon Jun 11 16:15:30 2012 for Sample Code by  + +doxygen 1.5.6
+ + diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classBird.html b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classBird.html new file mode 100644 index 00000000000..fef38de921b --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classBird.html @@ -0,0 +1,87 @@ + + +Sample Code: Bird Class Reference + + + + + +
+

Bird Class Reference

an abstract bird +More... +

+

+Inheritance diagram for Bird:
+
+ +

+ +Animal +Pigeon +RedKite + +
+ +

+List of all members. + + + + + +

Public Member Functions

 init (this)
 constructor
+


Detailed Description

+an abstract bird +

Definition at line 64 of file animals.lua.

+

Member Function Documentation

+ +
+
+ + + + + + + + + +
Bird::init (this   ) 
+
+
+ +

+constructor +

+ +

Reimplemented from Animal.

+ +

Reimplemented in Pigeon, and RedKite.

+ +

Definition at line 67 of file animals.lua.

+ +
+

+


The documentation for this class was generated from the following file: +
+
Generated on Mon Jun 11 16:15:30 2012 for Sample Code by  + +doxygen 1.5.6
+ + diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classBird.png b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classBird.png new file mode 100644 index 00000000000..d63f59dba48 Binary files /dev/null and b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classBird.png differ diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classCat-members.html b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classCat-members.html new file mode 100644 index 00000000000..8d9612fa3ce --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classCat-members.html @@ -0,0 +1,34 @@ + + +Sample Code: Member List + + + + + +
+

Cat Member List

This is the complete list of members for Cat, including all inherited members.

+ + + +
call(this)Animal
init(this)Cat
setKind(this, Kind)Animal

+
Generated on Mon Jun 11 16:15:30 2012 for Sample Code by  + +doxygen 1.5.6
+ + diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classCat.html b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classCat.html new file mode 100644 index 00000000000..8f8312de26d --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classCat.html @@ -0,0 +1,84 @@ + + +Sample Code: Cat Class Reference + + + + + +
+

Cat Class Reference

a subclassed mammal +More... +

+

+Inheritance diagram for Cat:
+
+ +

+ +Mammal +Animal + +
+ +

+List of all members. + + + + + +

Public Member Functions

 init (this)
 constructor
+


Detailed Description

+a subclassed mammal +

Definition at line 101 of file animals.lua.

+

Member Function Documentation

+ +
+
+ + + + + + + + + +
Cat::init (this   ) 
+
+
+ +

+constructor +

+ +

Reimplemented from Mammal.

+ +

Definition at line 104 of file animals.lua.

+ +
+

+


The documentation for this class was generated from the following file: +
+
Generated on Mon Jun 11 16:15:30 2012 for Sample Code by  + +doxygen 1.5.6
+ + diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classCat.png b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classCat.png new file mode 100644 index 00000000000..8500fb0b00a Binary files /dev/null and b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classCat.png differ diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classDog-members.html b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classDog-members.html new file mode 100644 index 00000000000..1bc803f974c --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classDog-members.html @@ -0,0 +1,34 @@ + + +Sample Code: Member List + + + + + +
+

Dog Member List

This is the complete list of members for Dog, including all inherited members.

+ + + +
call(this)Animal
init(this)Dog
setKind(this, Kind)Animal

+
Generated on Mon Jun 11 16:15:30 2012 for Sample Code by  + +doxygen 1.5.6
+ + diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classDog.html b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classDog.html new file mode 100644 index 00000000000..a02084640f5 --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classDog.html @@ -0,0 +1,84 @@ + + +Sample Code: Dog Class Reference + + + + + +
+

Dog Class Reference

another subclassed mammal +More... +

+

+Inheritance diagram for Dog:
+
+ +

+ +Mammal +Animal + +
+ +

+List of all members. + + + + + +

Public Member Functions

 init (this)
 constructor
+


Detailed Description

+another subclassed mammal +

Definition at line 111 of file animals.lua.

+

Member Function Documentation

+ +
+
+ + + + + + + + + +
Dog::init (this   ) 
+
+
+ +

+constructor +

+ +

Reimplemented from Mammal.

+ +

Definition at line 114 of file animals.lua.

+ +
+

+


The documentation for this class was generated from the following file: +
+
Generated on Mon Jun 11 16:15:30 2012 for Sample Code by  + +doxygen 1.5.6
+ + diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classDog.png b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classDog.png new file mode 100644 index 00000000000..6ba62396a49 Binary files /dev/null and b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classDog.png differ diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classMammal-members.html b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classMammal-members.html new file mode 100644 index 00000000000..147340920d9 --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classMammal-members.html @@ -0,0 +1,34 @@ + + +Sample Code: Member List + + + + + +
+

Mammal Member List

This is the complete list of members for Mammal, including all inherited members.

+ + + +
call(this)Animal
init(this)Mammal
setKind(this, Kind)Animal

+
Generated on Mon Jun 11 16:15:30 2012 for Sample Code by  + +doxygen 1.5.6
+ + diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classMammal.html b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classMammal.html new file mode 100644 index 00000000000..cc558db3f2a --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classMammal.html @@ -0,0 +1,87 @@ + + +Sample Code: Mammal Class Reference + + + + + +
+

Mammal Class Reference

a base mammal +More... +

+

+Inheritance diagram for Mammal:
+
+ +

+ +Animal +Cat +Dog + +
+ +

+List of all members. + + + + + +

Public Member Functions

 init (this)
 constructor
+


Detailed Description

+a base mammal +

Definition at line 93 of file animals.lua.

+

Member Function Documentation

+ +
+
+ + + + + + + + + +
Mammal::init (this   ) 
+
+
+ +

+constructor +

+ +

Reimplemented from Animal.

+ +

Reimplemented in Cat, and Dog.

+ +

Definition at line 96 of file animals.lua.

+ +
+

+


The documentation for this class was generated from the following file: +
+
Generated on Mon Jun 11 16:15:30 2012 for Sample Code by  + +doxygen 1.5.6
+ + diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classMammal.png b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classMammal.png new file mode 100644 index 00000000000..a736bde5a35 Binary files /dev/null and b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classMammal.png differ diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classPigeon-members.html b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classPigeon-members.html new file mode 100644 index 00000000000..2588b5bf714 --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classPigeon-members.html @@ -0,0 +1,34 @@ + + +Sample Code: Member List + + + + + +
+

Pigeon Member List

This is the complete list of members for Pigeon, including all inherited members.

+ + + +
call(this)Animal
init(this)Pigeon
setKind(this, Kind)Animal

+
Generated on Mon Jun 11 16:15:30 2012 for Sample Code by  + +doxygen 1.5.6
+ + diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classPigeon.html b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classPigeon.html new file mode 100644 index 00000000000..9e6802e73a9 --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classPigeon.html @@ -0,0 +1,84 @@ + + +Sample Code: Pigeon Class Reference + + + + + +
+

Pigeon Class Reference

a subclassed bird +More... +

+

+Inheritance diagram for Pigeon:
+
+ +

+ +Bird +Animal + +
+ +

+List of all members. + + + + + +

Public Member Functions

 init (this)
 constructor
+


Detailed Description

+a subclassed bird +

Definition at line 73 of file animals.lua.

+

Member Function Documentation

+ +
+
+ + + + + + + + + +
Pigeon::init (this   ) 
+
+
+ +

+constructor +

+ +

Reimplemented from Bird.

+ +

Definition at line 76 of file animals.lua.

+ +
+

+


The documentation for this class was generated from the following file: +
+
Generated on Mon Jun 11 16:15:30 2012 for Sample Code by  + +doxygen 1.5.6
+ + diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classPigeon.png b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classPigeon.png new file mode 100644 index 00000000000..dc73930253a Binary files /dev/null and b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classPigeon.png differ diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classRedKite-members.html b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classRedKite-members.html new file mode 100644 index 00000000000..67e73159194 --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classRedKite-members.html @@ -0,0 +1,34 @@ + + +Sample Code: Member List + + + + + +
+

RedKite Member List

This is the complete list of members for RedKite, including all inherited members.

+ + + +
call(this)Animal
init(this)RedKite
setKind(this, Kind)Animal

+
Generated on Mon Jun 11 16:15:30 2012 for Sample Code by  + +doxygen 1.5.6
+ + diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classRedKite.html b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classRedKite.html new file mode 100644 index 00000000000..49157afcdeb --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classRedKite.html @@ -0,0 +1,84 @@ + + +Sample Code: RedKite Class Reference + + + + + +
+

RedKite Class Reference

another subclassed bird +More... +

+

+Inheritance diagram for RedKite:
+
+ +

+ +Bird +Animal + +
+ +

+List of all members. + + + + + +

Public Member Functions

 init (this)
 constructor
+


Detailed Description

+another subclassed bird +

Definition at line 83 of file animals.lua.

+

Member Function Documentation

+ +
+
+ + + + + + + + + +
RedKite::init (this   ) 
+
+
+ +

+constructor +

+ +

Reimplemented from Bird.

+ +

Definition at line 86 of file animals.lua.

+ +
+

+


The documentation for this class was generated from the following file: +
+
Generated on Mon Jun 11 16:15:30 2012 for Sample Code by  + +doxygen 1.5.6
+ + diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classRedKite.png b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classRedKite.png new file mode 100644 index 00000000000..b286f8c415a Binary files /dev/null and b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/classRedKite.png differ diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/class_8lua-source.html b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/class_8lua-source.html new file mode 100644 index 00000000000..514134fd520 --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/class_8lua-source.html @@ -0,0 +1,106 @@ + + +Sample Code: class.lua Source File + + + + + +
Generated on Mon Jun 11 16:15:30 2012 for Sample Code by  + +doxygen 1.5.6
+ + diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/class_8lua.html b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/class_8lua.html new file mode 100644 index 00000000000..1920c3e0627 --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/class_8lua.html @@ -0,0 +1,79 @@ + + +Sample Code: class.lua File Reference + + + + + +
+

class.lua File Reference

enables classes in lua More... +

+ +

+Go to the source code of this file. + + + + + +

Functions

function class (BaseClass, ClassInitialiser)
 ``declare'' as class
+


Detailed Description

+enables classes in lua +

+ +

Definition in file class.lua.

+

Function Documentation

+ +
+
+ + + + + + + + + + + + + + + + + + +
function class (BaseClass ,
ClassInitialiser  
)
+
+
+ +

+``declare'' as class +

+use as:

 {lua}
+  TWibble = class()
+  function TWibble:init(instance)
+    self.instance = instance
+    -- more stuff here
+  end
+
+

Definition at line 36 of file class.lua.

+ +
+

+

+
Generated on Mon Jun 11 16:15:30 2012 for Sample Code by  + +doxygen 1.5.6
+ + diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/doxygen.css b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/doxygen.css new file mode 100644 index 00000000000..22c484301dd --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/doxygen.css @@ -0,0 +1,473 @@ +BODY,H1,H2,H3,H4,H5,H6,P,CENTER,TD,TH,UL,DL,DIV { + font-family: Geneva, Arial, Helvetica, sans-serif; +} +BODY,TD { + font-size: 90%; +} +H1 { + text-align: center; + font-size: 160%; +} +H2 { + font-size: 120%; +} +H3 { + font-size: 100%; +} +CAPTION { + font-weight: bold +} +DIV.qindex { + width: 100%; + background-color: #e8eef2; + border: 1px solid #84b0c7; + text-align: center; + margin: 2px; + padding: 2px; + line-height: 140%; +} +DIV.navpath { + width: 100%; + background-color: #e8eef2; + border: 1px solid #84b0c7; + text-align: center; + margin: 2px; + padding: 2px; + line-height: 140%; +} +DIV.navtab { + background-color: #e8eef2; + border: 1px solid #84b0c7; + text-align: center; + margin: 2px; + margin-right: 15px; + padding: 2px; +} +TD.navtab { + font-size: 70%; +} +A.qindex { + text-decoration: none; + font-weight: bold; + color: #1A419D; +} +A.qindex:visited { + text-decoration: none; + font-weight: bold; + color: #1A419D +} +A.qindex:hover { + text-decoration: none; + background-color: #ddddff; +} +A.qindexHL { + text-decoration: none; + font-weight: bold; + background-color: #6666cc; + color: #ffffff; + border: 1px double #9295C2; +} +A.qindexHL:hover { + text-decoration: none; + background-color: #6666cc; + color: #ffffff; +} +A.qindexHL:visited { + text-decoration: none; + background-color: #6666cc; + color: #ffffff +} +A.el { + text-decoration: none; + font-weight: bold +} +A.elRef { + font-weight: bold +} +A.code:link { + text-decoration: none; + font-weight: normal; + color: #0000FF +} +A.code:visited { + text-decoration: none; + font-weight: normal; + color: #0000FF +} +A.codeRef:link { + font-weight: normal; + color: #0000FF +} +A.codeRef:visited { + font-weight: normal; + color: #0000FF +} +A:hover { + text-decoration: none; + background-color: #f2f2ff +} +DL.el { + margin-left: -1cm +} +.fragment { + font-family: monospace, fixed; + font-size: 95%; +} +PRE.fragment { + border: 1px solid #CCCCCC; + background-color: #f5f5f5; + margin-top: 4px; + margin-bottom: 4px; + margin-left: 2px; + margin-right: 8px; + padding-left: 6px; + padding-right: 6px; + padding-top: 4px; + padding-bottom: 4px; +} +DIV.ah { + background-color: black; + font-weight: bold; + color: #ffffff; + margin-bottom: 3px; + margin-top: 3px +} + +DIV.groupHeader { + margin-left: 16px; + margin-top: 12px; + margin-bottom: 6px; + font-weight: bold; +} +DIV.groupText { + margin-left: 16px; + font-style: italic; + font-size: 90% +} +BODY { + background: white; + color: black; + margin-right: 20px; + margin-left: 20px; +} +TD.indexkey { + background-color: #e8eef2; + font-weight: bold; + padding-right : 10px; + padding-top : 2px; + padding-left : 10px; + padding-bottom : 2px; + margin-left : 0px; + margin-right : 0px; + margin-top : 2px; + margin-bottom : 2px; + border: 1px solid #CCCCCC; +} +TD.indexvalue { + background-color: #e8eef2; + font-style: italic; + padding-right : 10px; + padding-top : 2px; + padding-left : 10px; + padding-bottom : 2px; + margin-left : 0px; + margin-right : 0px; + margin-top : 2px; + margin-bottom : 2px; + border: 1px solid #CCCCCC; +} +TR.memlist { + background-color: #f0f0f0; +} +P.formulaDsp { + text-align: center; +} +IMG.formulaDsp { +} +IMG.formulaInl { + vertical-align: middle; +} +SPAN.keyword { color: #008000 } +SPAN.keywordtype { color: #604020 } +SPAN.keywordflow { color: #e08000 } +SPAN.comment { color: #800000 } +SPAN.preprocessor { color: #806020 } +SPAN.stringliteral { color: #002080 } +SPAN.charliteral { color: #008080 } +SPAN.vhdldigit { color: #ff00ff } +SPAN.vhdlchar { color: #000000 } +SPAN.vhdlkeyword { color: #700070 } +SPAN.vhdllogic { color: #ff0000 } + +.mdescLeft { + padding: 0px 8px 4px 8px; + font-size: 80%; + font-style: italic; + background-color: #FAFAFA; + border-top: 1px none #E0E0E0; + border-right: 1px none #E0E0E0; + border-bottom: 1px none #E0E0E0; + border-left: 1px none #E0E0E0; + margin: 0px; +} +.mdescRight { + padding: 0px 8px 4px 8px; + font-size: 80%; + font-style: italic; + background-color: #FAFAFA; + border-top: 1px none #E0E0E0; + border-right: 1px none #E0E0E0; + border-bottom: 1px none #E0E0E0; + border-left: 1px none #E0E0E0; + margin: 0px; +} +.memItemLeft { + padding: 1px 0px 0px 8px; + margin: 4px; + border-top-width: 1px; + border-right-width: 1px; + border-bottom-width: 1px; + border-left-width: 1px; + border-top-color: #E0E0E0; + border-right-color: #E0E0E0; + border-bottom-color: #E0E0E0; + border-left-color: #E0E0E0; + border-top-style: solid; + border-right-style: none; + border-bottom-style: none; + border-left-style: none; + background-color: #FAFAFA; + font-size: 80%; +} +.memItemRight { + padding: 1px 8px 0px 8px; + margin: 4px; + border-top-width: 1px; + border-right-width: 1px; + border-bottom-width: 1px; + border-left-width: 1px; + border-top-color: #E0E0E0; + border-right-color: #E0E0E0; + border-bottom-color: #E0E0E0; + border-left-color: #E0E0E0; + border-top-style: solid; + border-right-style: none; + border-bottom-style: none; + border-left-style: none; + background-color: #FAFAFA; + font-size: 80%; +} +.memTemplItemLeft { + padding: 1px 0px 0px 8px; + margin: 4px; + border-top-width: 1px; + border-right-width: 1px; + border-bottom-width: 1px; + border-left-width: 1px; + border-top-color: #E0E0E0; + border-right-color: #E0E0E0; + border-bottom-color: #E0E0E0; + border-left-color: #E0E0E0; + border-top-style: none; + border-right-style: none; + border-bottom-style: none; + border-left-style: none; + background-color: #FAFAFA; + font-size: 80%; +} +.memTemplItemRight { + padding: 1px 8px 0px 8px; + margin: 4px; + border-top-width: 1px; + border-right-width: 1px; + border-bottom-width: 1px; + border-left-width: 1px; + border-top-color: #E0E0E0; + border-right-color: #E0E0E0; + border-bottom-color: #E0E0E0; + border-left-color: #E0E0E0; + border-top-style: none; + border-right-style: none; + border-bottom-style: none; + border-left-style: none; + background-color: #FAFAFA; + font-size: 80%; +} +.memTemplParams { + padding: 1px 0px 0px 8px; + margin: 4px; + border-top-width: 1px; + border-right-width: 1px; + border-bottom-width: 1px; + border-left-width: 1px; + border-top-color: #E0E0E0; + border-right-color: #E0E0E0; + border-bottom-color: #E0E0E0; + border-left-color: #E0E0E0; + border-top-style: solid; + border-right-style: none; + border-bottom-style: none; + border-left-style: none; + color: #606060; + background-color: #FAFAFA; + font-size: 80%; +} +.search { + color: #003399; + font-weight: bold; +} +FORM.search { + margin-bottom: 0px; + margin-top: 0px; +} +INPUT.search { + font-size: 75%; + color: #000080; + font-weight: normal; + background-color: #e8eef2; +} +TD.tiny { + font-size: 75%; +} +a { + color: #1A41A8; +} +a:visited { + color: #2A3798; +} +.dirtab { + padding: 4px; + border-collapse: collapse; + border: 1px solid #84b0c7; +} +TH.dirtab { + background: #e8eef2; + font-weight: bold; +} +HR { + height: 1px; + border: none; + border-top: 1px solid black; +} + +/* Style for detailed member documentation */ +.memtemplate { + font-size: 80%; + color: #606060; + font-weight: normal; + margin-left: 3px; +} +.memnav { + background-color: #e8eef2; + border: 1px solid #84b0c7; + text-align: center; + margin: 2px; + margin-right: 15px; + padding: 2px; +} +.memitem { + padding: 4px; + background-color: #eef3f5; + border-width: 1px; + border-style: solid; + border-color: #dedeee; + -moz-border-radius: 8px 8px 8px 8px; +} +.memname { + white-space: nowrap; + font-weight: bold; +} +.memdoc{ + padding-left: 10px; +} +.memproto { + background-color: #d5e1e8; + width: 100%; + border-width: 1px; + border-style: solid; + border-color: #84b0c7; + font-weight: bold; + -moz-border-radius: 8px 8px 8px 8px; +} +.paramkey { + text-align: right; +} +.paramtype { + white-space: nowrap; +} +.paramname { + color: #602020; + font-style: italic; + white-space: nowrap; +} +/* End Styling for detailed member documentation */ + +/* for the tree view */ +.ftvtree { + font-family: sans-serif; + margin:0.5em; +} +/* these are for tree view when used as main index */ +.directory { + font-size: 9pt; + font-weight: bold; +} +.directory h3 { + margin: 0px; + margin-top: 1em; + font-size: 11pt; +} + +/* The following two styles can be used to replace the root node title */ +/* with an image of your choice. Simply uncomment the next two styles, */ +/* specify the name of your image and be sure to set 'height' to the */ +/* proper pixel height of your image. */ + +/* .directory h3.swap { */ +/* height: 61px; */ +/* background-repeat: no-repeat; */ +/* background-image: url("yourimage.gif"); */ +/* } */ +/* .directory h3.swap span { */ +/* display: none; */ +/* } */ + +.directory > h3 { + margin-top: 0; +} +.directory p { + margin: 0px; + white-space: nowrap; +} +.directory div { + display: none; + margin: 0px; +} +.directory img { + vertical-align: -30%; +} +/* these are for tree view when not used as main index */ +.directory-alt { + font-size: 100%; + font-weight: bold; +} +.directory-alt h3 { + margin: 0px; + margin-top: 1em; + font-size: 11pt; +} +.directory-alt > h3 { + margin-top: 0; +} +.directory-alt p { + margin: 0px; + white-space: nowrap; +} +.directory-alt div { + display: none; + margin: 0px; +} +.directory-alt img { + vertical-align: -30%; +} + diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/doxygen.png b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/doxygen.png new file mode 100644 index 00000000000..f0a274bbaff Binary files /dev/null and b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/doxygen.png differ diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/files.html b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/files.html new file mode 100644 index 00000000000..3f47f1dcf7b --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/files.html @@ -0,0 +1,34 @@ + + +Sample Code: File Index + + + + + +
+

File List

Here is a list of all files with brief descriptions: + + + +
animals.lua [code]Test some classes
class.lua [code]Enables classes in lua
main.lua [code]Test code
+
+
Generated on Mon Jun 11 16:15:30 2012 for Sample Code by  + +doxygen 1.5.6
+ + diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/functions.html b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/functions.html new file mode 100644 index 00000000000..849f965d8e1 --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/functions.html @@ -0,0 +1,52 @@ + + +Sample Code: Class Members + + + + + +
+Here is a list of all class members with links to the classes they belong to: +

+

+
+
Generated on Mon Jun 11 16:15:30 2012 for Sample Code by  + +doxygen 1.5.6
+ + diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/functions_func.html b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/functions_func.html new file mode 100644 index 00000000000..9e6da114996 --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/functions_func.html @@ -0,0 +1,52 @@ + + +Sample Code: Class Members - Functions + + + + + +
+  +

+

+
+
Generated on Mon Jun 11 16:15:30 2012 for Sample Code by  + +doxygen 1.5.6
+ + diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/globals.html b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/globals.html new file mode 100644 index 00000000000..05674dcebc6 --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/globals.html @@ -0,0 +1,45 @@ + + +Sample Code: Class Members + + + + + +
+Here is a list of all file members with links to the files they belong to: +

+

+
+
Generated on Mon Jun 11 16:15:30 2012 for Sample Code by  + +doxygen 1.5.6
+ + diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/globals_func.html b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/globals_func.html new file mode 100644 index 00000000000..56b7a593ebc --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/globals_func.html @@ -0,0 +1,45 @@ + + +Sample Code: Class Members + + + + + +
+  +

+

+
+
Generated on Mon Jun 11 16:15:30 2012 for Sample Code by  + +doxygen 1.5.6
+ + diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/hierarchy.html b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/hierarchy.html new file mode 100644 index 00000000000..9ad191402ab --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/hierarchy.html @@ -0,0 +1,45 @@ + + +Sample Code: Hierarchical Index + + + + + +
+

Class Hierarchy

This inheritance list is sorted roughly, but not completely, alphabetically: +
+
Generated on Mon Jun 11 16:15:30 2012 for Sample Code by  + +doxygen 1.5.6
+ + diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/index.html b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/index.html new file mode 100644 index 00000000000..b309f15c5e9 --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/index.html @@ -0,0 +1,25 @@ + + +Sample Code: Main Page + + + + + +
+

Sample Code Documentation

+

+

0.1 20120518

Some test code. This shows a hierachy of classes. For this example we do animals.
+
Generated on Mon Jun 11 16:15:30 2012 for Sample Code by  + +doxygen 1.5.6
+ + diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/main_8lua-source.html b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/main_8lua-source.html new file mode 100644 index 00000000000..a13a1dcc537 --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/main_8lua-source.html @@ -0,0 +1,63 @@ + + +Sample Code: main.lua Source File + + + + + +
Generated on Mon Jun 11 16:15:30 2012 for Sample Code by  + +doxygen 1.5.6
+ + diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/main_8lua.html b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/main_8lua.html new file mode 100644 index 00000000000..ae6b738aa25 --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/main_8lua.html @@ -0,0 +1,35 @@ + + +Sample Code: main.lua File Reference + + + + + +
+

main.lua File Reference

test code More... +

+ +

+Go to the source code of this file. + +
+


Detailed Description

+test code +

+ +

Definition in file main.lua.

+
+
Generated on Mon Jun 11 16:15:30 2012 for Sample Code by  + +doxygen 1.5.6
+ + diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/tab_b.gif b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/tab_b.gif new file mode 100644 index 00000000000..0d623483ffd Binary files /dev/null and b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/tab_b.gif differ diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/tab_l.gif b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/tab_l.gif new file mode 100644 index 00000000000..9b1e6337c92 Binary files /dev/null and b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/tab_l.gif differ diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/tab_r.gif b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/tab_r.gif new file mode 100644 index 00000000000..ce9dd9f533c Binary files /dev/null and b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/tab_r.gif differ diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/tabs.css b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/tabs.css new file mode 100644 index 00000000000..95f00a91da3 --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/examples/lua/docs/html/tabs.css @@ -0,0 +1,102 @@ +/* tabs styles, based on http://www.alistapart.com/articles/slidingdoors */ + +DIV.tabs +{ + float : left; + width : 100%; + background : url("tab_b.gif") repeat-x bottom; + margin-bottom : 4px; +} + +DIV.tabs UL +{ + margin : 0px; + padding-left : 10px; + list-style : none; +} + +DIV.tabs LI, DIV.tabs FORM +{ + display : inline; + margin : 0px; + padding : 0px; +} + +DIV.tabs FORM +{ + float : right; +} + +DIV.tabs A +{ + float : left; + background : url("tab_r.gif") no-repeat right top; + border-bottom : 1px solid #84B0C7; + font-size : x-small; + font-weight : bold; + text-decoration : none; +} + +DIV.tabs A:hover +{ + background-position: 100% -150px; +} + +DIV.tabs A:link, DIV.tabs A:visited, +DIV.tabs A:active, DIV.tabs A:hover +{ + color: #1A419D; +} + +DIV.tabs SPAN +{ + float : left; + display : block; + background : url("tab_l.gif") no-repeat left top; + padding : 5px 9px; + white-space : nowrap; +} + +DIV.tabs INPUT +{ + float : right; + display : inline; + font-size : 1em; +} + +DIV.tabs TD +{ + font-size : x-small; + font-weight : bold; + text-decoration : none; +} + + + +/* Commented Backslash Hack hides rule from IE5-Mac \*/ +DIV.tabs SPAN {float : none;} +/* End IE5-Mac hack */ + +DIV.tabs A:hover SPAN +{ + background-position: 0% -150px; +} + +DIV.tabs LI.current A +{ + background-position: 100% -150px; + border-width : 0px; +} + +DIV.tabs LI.current SPAN +{ + background-position: 0% -150px; + padding-bottom : 6px; +} + +DIV.navpath +{ + background : none; + border : none; + border-bottom : 1px solid #84B0C7; +} diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/lua/main.lua b/Master/texmf-dist/doc/support/lua2dox/examples/lua/main.lua new file mode 100644 index 00000000000..6f5245e98bd --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/examples/lua/main.lua @@ -0,0 +1,42 @@ +---- Copyright 2012 Simon Dales +-- +-- This work may be distributed and/or modified under the +-- conditions of the LaTeX Project Public License, either version 1.3 +-- of this license or (at your option) any later version. +-- The latest version of this license is in +-- http://www.latex-project.org/lppl.txt +-- +-- This work has the LPPL maintenance status `maintained'. +-- +-- The Current Maintainer of this work is Simon Dales. +-- + +--[[! + \file + \brief test code + + ]] + +--[[! + \mainpage + + Some test code. + This shows a hierachy of classes. + For this example we do animals. + + ]] + +require 'animals' + +-- main +local animals = { + Cat() + ,Dog() + ,Bird() + ,RedKite() + ,Pigeon() + } + +for k,v in pairs(animals) do + v:call() +end diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/php/Doxyfile b/Master/texmf-dist/doc/support/lua2dox/examples/php/Doxyfile new file mode 100644 index 00000000000..54b39f7bcc5 --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/examples/php/Doxyfile @@ -0,0 +1,1421 @@ +# Doxyfile 1.5.6 + +# This file describes the settings to be used by the documentation system +# doxygen (www.doxygen.org) for a project +# +# All text after a hash (#) is considered a comment and will be ignored +# The format is: +# TAG = value [value, ...] +# For lists items can also be appended using: +# TAG += value [value, ...] +# Values that contain spaces should be placed between quotes (" ") + +#--------------------------------------------------------------------------- +# Project related configuration options +#--------------------------------------------------------------------------- + +# This tag specifies the encoding used for all characters in the config file +# that follow. The default is UTF-8 which is also the encoding used for all +# text before the first occurrence of this tag. Doxygen uses libiconv (or the +# iconv built into libc) for the transcoding. See +# http://www.gnu.org/software/libiconv for the list of possible encodings. + +DOXYFILE_ENCODING = UTF-8 + +# The PROJECT_NAME tag is a single word (or a sequence of words surrounded +# by quotes) that should identify the project. + +PROJECT_NAME = "Sample Code (PHP)" + +# The PROJECT_NUMBER tag can be used to enter a project or revision number. +# This could be handy for archiving the generated documentation or +# if some version control system is used. + +PROJECT_NUMBER = "0.1 20120518" + +# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) +# base path where the generated documentation will be put. +# If a relative path is entered, it will be relative to the location +# where doxygen was started. If left blank the current directory will be used. + +OUTPUT_DIRECTORY = docs + +# If the CREATE_SUBDIRS tag is set to YES, then doxygen will create +# 4096 sub-directories (in 2 levels) under the output directory of each output +# format and will distribute the generated files over these directories. +# Enabling this option can be useful when feeding doxygen a huge amount of +# source files, where putting all generated files in the same directory would +# otherwise cause performance problems for the file system. + +CREATE_SUBDIRS = NO + +# The OUTPUT_LANGUAGE tag is used to specify the language in which all +# documentation generated by doxygen is written. Doxygen will use this +# information to generate all constant output in the proper language. +# The default language is English, other supported languages are: +# Afrikaans, Arabic, Brazilian, Catalan, Chinese, Chinese-Traditional, +# Croatian, Czech, Danish, Dutch, Farsi, Finnish, French, German, Greek, +# Hungarian, Italian, Japanese, Japanese-en (Japanese with English messages), +# Korean, Korean-en, Lithuanian, Norwegian, Macedonian, Persian, Polish, +# Portuguese, Romanian, Russian, Serbian, Slovak, Slovene, Spanish, Swedish, +# and Ukrainian. + +OUTPUT_LANGUAGE = English + +# If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will +# include brief member descriptions after the members that are listed in +# the file and class documentation (similar to JavaDoc). +# Set to NO to disable this. + +BRIEF_MEMBER_DESC = YES + +# If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend +# the brief description of a member or function before the detailed description. +# Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the +# brief descriptions will be completely suppressed. + +REPEAT_BRIEF = YES + +# This tag implements a quasi-intelligent brief description abbreviator +# that is used to form the text in various listings. Each string +# in this list, if found as the leading text of the brief description, will be +# stripped from the text and the result after processing the whole list, is +# used as the annotated text. Otherwise, the brief description is used as-is. +# If left blank, the following values are used ("$name" is automatically +# replaced with the name of the entity): "The $name class" "The $name widget" +# "The $name file" "is" "provides" "specifies" "contains" +# "represents" "a" "an" "the" + +ABBREVIATE_BRIEF = + +# If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then +# Doxygen will generate a detailed section even if there is only a brief +# description. + +ALWAYS_DETAILED_SEC = NO + +# If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all +# inherited members of a class in the documentation of that class as if those +# members were ordinary class members. Constructors, destructors and assignment +# operators of the base classes will not be shown. + +INLINE_INHERITED_MEMB = NO + +# If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full +# path before files name in the file list and in the header files. If set +# to NO the shortest path that makes the file name unique will be used. + +FULL_PATH_NAMES = YES + +# If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag +# can be used to strip a user-defined part of the path. Stripping is +# only done if one of the specified strings matches the left-hand part of +# the path. The tag can be used to show relative paths in the file list. +# If left blank the directory from which doxygen is run is used as the +# path to strip. + +STRIP_FROM_PATH = + +# The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of +# the path mentioned in the documentation of a class, which tells +# the reader which header file to include in order to use a class. +# If left blank only the name of the header file containing the class +# definition is used. Otherwise one should specify the include paths that +# are normally passed to the compiler using the -I flag. + +STRIP_FROM_INC_PATH = + +# If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter +# (but less readable) file names. This can be useful is your file systems +# doesn't support long names like on DOS, Mac, or CD-ROM. + +SHORT_NAMES = NO + +# If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen +# will interpret the first line (until the first dot) of a JavaDoc-style +# comment as the brief description. If set to NO, the JavaDoc +# comments will behave just like regular Qt-style comments +# (thus requiring an explicit @brief command for a brief description.) + +JAVADOC_AUTOBRIEF = NO + +# If the QT_AUTOBRIEF tag is set to YES then Doxygen will +# interpret the first line (until the first dot) of a Qt-style +# comment as the brief description. If set to NO, the comments +# will behave just like regular Qt-style comments (thus requiring +# an explicit \brief command for a brief description.) + +QT_AUTOBRIEF = NO + +# The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen +# treat a multi-line C++ special comment block (i.e. a block of //! or /// +# comments) as a brief description. This used to be the default behaviour. +# The new default is to treat a multi-line C++ comment block as a detailed +# description. Set this tag to YES if you prefer the old behaviour instead. + +MULTILINE_CPP_IS_BRIEF = NO + +# If the DETAILS_AT_TOP tag is set to YES then Doxygen +# will output the detailed description near the top, like JavaDoc. +# If set to NO, the detailed description appears after the member +# documentation. + +DETAILS_AT_TOP = NO + +# If the INHERIT_DOCS tag is set to YES (the default) then an undocumented +# member inherits the documentation from any documented member that it +# re-implements. + +INHERIT_DOCS = YES + +# If the SEPARATE_MEMBER_PAGES tag is set to YES, then doxygen will produce +# a new page for each member. If set to NO, the documentation of a member will +# be part of the file/class/namespace that contains it. + +SEPARATE_MEMBER_PAGES = NO + +# The TAB_SIZE tag can be used to set the number of spaces in a tab. +# Doxygen uses this value to replace tabs by spaces in code fragments. + +TAB_SIZE = 2 + +# This tag can be used to specify a number of aliases that acts +# as commands in the documentation. An alias has the form "name=value". +# For example adding "sideeffect=\par Side Effects:\n" will allow you to +# put the command \sideeffect (or @sideeffect) in the documentation, which +# will result in a user-defined paragraph with heading "Side Effects:". +# You can put \n's in the value part of an alias to insert newlines. + +ALIASES = + +# Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C +# sources only. Doxygen will then generate output that is more tailored for C. +# For instance, some of the names that are used will be different. The list +# of all members will be omitted, etc. + +OPTIMIZE_OUTPUT_FOR_C = NO + +# Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java +# sources only. Doxygen will then generate output that is more tailored for +# Java. For instance, namespaces will be presented as packages, qualified +# scopes will look different, etc. + +OPTIMIZE_OUTPUT_JAVA = NO + +# Set the OPTIMIZE_FOR_FORTRAN tag to YES if your project consists of Fortran +# sources only. Doxygen will then generate output that is more tailored for +# Fortran. + +OPTIMIZE_FOR_FORTRAN = NO + +# Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL +# sources. Doxygen will then generate output that is tailored for +# VHDL. + +OPTIMIZE_OUTPUT_VHDL = NO + +# If you use STL classes (i.e. std::string, std::vector, etc.) but do not want +# to include (a tag file for) the STL sources as input, then you should +# set this tag to YES in order to let doxygen match functions declarations and +# definitions whose arguments contain STL classes (e.g. func(std::string); v.s. +# func(std::string) {}). This also make the inheritance and collaboration +# diagrams that involve STL classes more complete and accurate. + +BUILTIN_STL_SUPPORT = NO + +# If you use Microsoft's C++/CLI language, you should set this option to YES to +# enable parsing support. + +CPP_CLI_SUPPORT = NO + +# Set the SIP_SUPPORT tag to YES if your project consists of sip sources only. +# Doxygen will parse them like normal C++ but will assume all classes use public +# instead of private inheritance when no explicit protection keyword is present. + +SIP_SUPPORT = NO + +# For Microsoft's IDL there are propget and propput attributes to indicate getter +# and setter methods for a property. Setting this option to YES (the default) +# will make doxygen to replace the get and set methods by a property in the +# documentation. This will only work if the methods are indeed getting or +# setting a simple type. If this is not the case, or you want to show the +# methods anyway, you should set this option to NO. + +IDL_PROPERTY_SUPPORT = YES + +# If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC +# tag is set to YES, then doxygen will reuse the documentation of the first +# member in the group (if any) for the other members of the group. By default +# all members of a group must be documented explicitly. + +DISTRIBUTE_GROUP_DOC = NO + +# Set the SUBGROUPING tag to YES (the default) to allow class member groups of +# the same type (for instance a group of public functions) to be put as a +# subgroup of that type (e.g. under the Public Functions section). Set it to +# NO to prevent subgrouping. Alternatively, this can be done per class using +# the \nosubgrouping command. + +SUBGROUPING = YES + +# When TYPEDEF_HIDES_STRUCT is enabled, a typedef of a struct, union, or enum +# is documented as struct, union, or enum with the name of the typedef. So +# typedef struct TypeS {} TypeT, will appear in the documentation as a struct +# with name TypeT. When disabled the typedef will appear as a member of a file, +# namespace, or class. And the struct will be named TypeS. This can typically +# be useful for C code in case the coding convention dictates that all compound +# types are typedef'ed and only the typedef is referenced, never the tag name. + +TYPEDEF_HIDES_STRUCT = NO + +#--------------------------------------------------------------------------- +# Build related configuration options +#--------------------------------------------------------------------------- + +# If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in +# documentation are documented, even if no documentation was available. +# Private class members and static file members will be hidden unless +# the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES + +#EXTRACT_ALL = NO +EXTRACT_ALL = yes + +# If the EXTRACT_PRIVATE tag is set to YES all private members of a class +# will be included in the documentation. + +EXTRACT_PRIVATE = NO + +# If the EXTRACT_STATIC tag is set to YES all static members of a file +# will be included in the documentation. + +EXTRACT_STATIC = NO + +# If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs) +# defined locally in source files will be included in the documentation. +# If set to NO only classes defined in header files are included. + +EXTRACT_LOCAL_CLASSES = YES + +# This flag is only useful for Objective-C code. When set to YES local +# methods, which are defined in the implementation section but not in +# the interface are included in the documentation. +# If set to NO (the default) only methods in the interface are included. + +EXTRACT_LOCAL_METHODS = NO + +# If this flag is set to YES, the members of anonymous namespaces will be +# extracted and appear in the documentation as a namespace called +# 'anonymous_namespace{file}', where file will be replaced with the base +# name of the file that contains the anonymous namespace. By default +# anonymous namespace are hidden. + +EXTRACT_ANON_NSPACES = NO + +# If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all +# undocumented members of documented classes, files or namespaces. +# If set to NO (the default) these members will be included in the +# various overviews, but no documentation section is generated. +# This option has no effect if EXTRACT_ALL is enabled. + +HIDE_UNDOC_MEMBERS = NO + +# If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all +# undocumented classes that are normally visible in the class hierarchy. +# If set to NO (the default) these classes will be included in the various +# overviews. This option has no effect if EXTRACT_ALL is enabled. + +HIDE_UNDOC_CLASSES = NO + +# If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all +# friend (class|struct|union) declarations. +# If set to NO (the default) these declarations will be included in the +# documentation. + +HIDE_FRIEND_COMPOUNDS = NO + +# If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any +# documentation blocks found inside the body of a function. +# If set to NO (the default) these blocks will be appended to the +# function's detailed documentation block. + +HIDE_IN_BODY_DOCS = NO + +# The INTERNAL_DOCS tag determines if documentation +# that is typed after a \internal command is included. If the tag is set +# to NO (the default) then the documentation will be excluded. +# Set it to YES to include the internal documentation. + +INTERNAL_DOCS = NO + +# If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate +# file names in lower-case letters. If set to YES upper-case letters are also +# allowed. This is useful if you have classes or files whose names only differ +# in case and if your file system supports case sensitive file names. Windows +# and Mac users are advised to set this option to NO. + +CASE_SENSE_NAMES = YES + +# If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen +# will show members with their full class and namespace scopes in the +# documentation. If set to YES the scope will be hidden. + +HIDE_SCOPE_NAMES = NO + +# If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen +# will put a list of the files that are included by a file in the documentation +# of that file. + +SHOW_INCLUDE_FILES = YES + +# If the INLINE_INFO tag is set to YES (the default) then a tag [inline] +# is inserted in the documentation for inline members. + +INLINE_INFO = YES + +# If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen +# will sort the (detailed) documentation of file and class members +# alphabetically by member name. If set to NO the members will appear in +# declaration order. + +SORT_MEMBER_DOCS = YES + +# If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the +# brief documentation of file, namespace and class members alphabetically +# by member name. If set to NO (the default) the members will appear in +# declaration order. + +#SORT_BRIEF_DOCS = NO +SORT_BRIEF_DOCS = yes + +# If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the +# hierarchy of group names into alphabetical order. If set to NO (the default) +# the group names will appear in their defined order. + +SORT_GROUP_NAMES = NO + +# If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be +# sorted by fully-qualified names, including namespaces. If set to +# NO (the default), the class list will be sorted only by class name, +# not including the namespace part. +# Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES. +# Note: This option applies only to the class list, not to the +# alphabetical list. + +SORT_BY_SCOPE_NAME = NO + +# The GENERATE_TODOLIST tag can be used to enable (YES) or +# disable (NO) the todo list. This list is created by putting \todo +# commands in the documentation. + +GENERATE_TODOLIST = YES + +# The GENERATE_TESTLIST tag can be used to enable (YES) or +# disable (NO) the test list. This list is created by putting \test +# commands in the documentation. + +GENERATE_TESTLIST = YES + +# The GENERATE_BUGLIST tag can be used to enable (YES) or +# disable (NO) the bug list. This list is created by putting \bug +# commands in the documentation. + +GENERATE_BUGLIST = YES + +# The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or +# disable (NO) the deprecated list. This list is created by putting +# \deprecated commands in the documentation. + +GENERATE_DEPRECATEDLIST= YES + +# The ENABLED_SECTIONS tag can be used to enable conditional +# documentation sections, marked by \if sectionname ... \endif. + +ENABLED_SECTIONS = + +# The MAX_INITIALIZER_LINES tag determines the maximum number of lines +# the initial value of a variable or define consists of for it to appear in +# the documentation. If the initializer consists of more lines than specified +# here it will be hidden. Use a value of 0 to hide initializers completely. +# The appearance of the initializer of individual variables and defines in the +# documentation can be controlled using \showinitializer or \hideinitializer +# command in the documentation regardless of this setting. + +MAX_INITIALIZER_LINES = 30 + +# Set the SHOW_USED_FILES tag to NO to disable the list of files generated +# at the bottom of the documentation of classes and structs. If set to YES the +# list will mention the files that were used to generate the documentation. + +SHOW_USED_FILES = YES + +# If the sources in your project are distributed over multiple directories +# then setting the SHOW_DIRECTORIES tag to YES will show the directory hierarchy +# in the documentation. The default is NO. + +SHOW_DIRECTORIES = NO + +# Set the SHOW_FILES tag to NO to disable the generation of the Files page. +# This will remove the Files entry from the Quick Index and from the +# Folder Tree View (if specified). The default is YES. + +SHOW_FILES = YES + +# Set the SHOW_NAMESPACES tag to NO to disable the generation of the +# Namespaces page. This will remove the Namespaces entry from the Quick Index +# and from the Folder Tree View (if specified). The default is YES. + +SHOW_NAMESPACES = YES + +# The FILE_VERSION_FILTER tag can be used to specify a program or script that +# doxygen should invoke to get the current version for each file (typically from +# the version control system). Doxygen will invoke the program by executing (via +# popen()) the command , where is the value of +# the FILE_VERSION_FILTER tag, and is the name of an input file +# provided by doxygen. Whatever the program writes to standard output +# is used as the file version. See the manual for examples. + +FILE_VERSION_FILTER = + +#--------------------------------------------------------------------------- +# configuration options related to warning and progress messages +#--------------------------------------------------------------------------- + +# The QUIET tag can be used to turn on/off the messages that are generated +# by doxygen. Possible values are YES and NO. If left blank NO is used. + +QUIET = NO + +# The WARNINGS tag can be used to turn on/off the warning messages that are +# generated by doxygen. Possible values are YES and NO. If left blank +# NO is used. + +WARNINGS = YES + +# If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings +# for undocumented members. If EXTRACT_ALL is set to YES then this flag will +# automatically be disabled. + +WARN_IF_UNDOCUMENTED = YES + +# If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for +# potential errors in the documentation, such as not documenting some +# parameters in a documented function, or documenting parameters that +# don't exist or using markup commands wrongly. + +WARN_IF_DOC_ERROR = YES + +# This WARN_NO_PARAMDOC option can be abled to get warnings for +# functions that are documented, but have no documentation for their parameters +# or return value. If set to NO (the default) doxygen will only warn about +# wrong or incomplete parameter documentation, but not about the absence of +# documentation. + +WARN_NO_PARAMDOC = NO + +# The WARN_FORMAT tag determines the format of the warning messages that +# doxygen can produce. The string should contain the $file, $line, and $text +# tags, which will be replaced by the file and line number from which the +# warning originated and the warning text. Optionally the format may contain +# $version, which will be replaced by the version of the file (if it could +# be obtained via FILE_VERSION_FILTER) + +WARN_FORMAT = "$file:$line: $text" + +# The WARN_LOGFILE tag can be used to specify a file to which warning +# and error messages should be written. If left blank the output is written +# to stderr. + +WARN_LOGFILE = + +#--------------------------------------------------------------------------- +# configuration options related to the input files +#--------------------------------------------------------------------------- + +# The INPUT tag can be used to specify the files and/or directories that contain +# documented source files. You may enter file names like "myfile.cpp" or +# directories like "/usr/src/myproject". Separate the files or directories +# with spaces. + +INPUT = + +# This tag can be used to specify the character encoding of the source files +# that doxygen parses. Internally doxygen uses the UTF-8 encoding, which is +# also the default input encoding. Doxygen uses libiconv (or the iconv built +# into libc) for the transcoding. See http://www.gnu.org/software/libiconv for +# the list of possible encodings. + +INPUT_ENCODING = UTF-8 + +# If the value of the INPUT tag contains directories, you can use the +# FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp +# and *.h) to filter out the source-files in the directories. If left +# blank the following patterns are tested: +# *.c *.cc *.cxx *.cpp *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx +# *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm *.py *.f90 + +FILE_PATTERNS = + +# The RECURSIVE tag can be used to turn specify whether or not subdirectories +# should be searched for input files as well. Possible values are YES and NO. +# If left blank NO is used. + +RECURSIVE = NO + +# The EXCLUDE tag can be used to specify files and/or directories that should +# excluded from the INPUT source files. This way you can easily exclude a +# subdirectory from a directory tree whose root is specified with the INPUT tag. + +EXCLUDE = + +# The EXCLUDE_SYMLINKS tag can be used select whether or not files or +# directories that are symbolic links (a Unix filesystem feature) are excluded +# from the input. + +EXCLUDE_SYMLINKS = NO + +# If the value of the INPUT tag contains directories, you can use the +# EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude +# certain files from those directories. Note that the wildcards are matched +# against the file with absolute path, so to exclude all test directories +# for example use the pattern */test/* + +EXCLUDE_PATTERNS = + +# The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names +# (namespaces, classes, functions, etc.) that should be excluded from the +# output. The symbol name can be a fully qualified name, a word, or if the +# wildcard * is used, a substring. Examples: ANamespace, AClass, +# AClass::ANamespace, ANamespace::*Test + +EXCLUDE_SYMBOLS = + +# The EXAMPLE_PATH tag can be used to specify one or more files or +# directories that contain example code fragments that are included (see +# the \include command). + +EXAMPLE_PATH = + +# If the value of the EXAMPLE_PATH tag contains directories, you can use the +# EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp +# and *.h) to filter out the source-files in the directories. If left +# blank all files are included. + +EXAMPLE_PATTERNS = + +# If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be +# searched for input files to be used with the \include or \dontinclude +# commands irrespective of the value of the RECURSIVE tag. +# Possible values are YES and NO. If left blank NO is used. + +EXAMPLE_RECURSIVE = NO + +# The IMAGE_PATH tag can be used to specify one or more files or +# directories that contain image that are included in the documentation (see +# the \image command). + +IMAGE_PATH = + +# The INPUT_FILTER tag can be used to specify a program that doxygen should +# invoke to filter for each input file. Doxygen will invoke the filter program +# by executing (via popen()) the command , where +# is the value of the INPUT_FILTER tag, and is the name of an +# input file. Doxygen will then use the output that the filter program writes +# to standard output. If FILTER_PATTERNS is specified, this tag will be +# ignored. + +INPUT_FILTER = + +# The FILTER_PATTERNS tag can be used to specify filters on a per file pattern +# basis. Doxygen will compare the file name with each pattern and apply the +# filter if there is a match. The filters are a list of the form: +# pattern=filter (like *.cpp=my_cpp_filter). See INPUT_FILTER for further +# info on how filters are used. If FILTER_PATTERNS is empty, INPUT_FILTER +# is applied to all files. + +FILTER_PATTERNS = + +# If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using +# INPUT_FILTER) will be used to filter the input files when producing source +# files to browse (i.e. when SOURCE_BROWSER is set to YES). + +FILTER_SOURCE_FILES = NO + +#--------------------------------------------------------------------------- +# configuration options related to source browsing +#--------------------------------------------------------------------------- + +# If the SOURCE_BROWSER tag is set to YES then a list of source files will +# be generated. Documented entities will be cross-referenced with these sources. +# Note: To get rid of all source code in the generated output, make sure also +# VERBATIM_HEADERS is set to NO. + +#SOURCE_BROWSER = NO +SOURCE_BROWSER = yes + +# Setting the INLINE_SOURCES tag to YES will include the body +# of functions and classes directly in the documentation. + +INLINE_SOURCES = NO + +# Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct +# doxygen to hide any special comment blocks from generated source code +# fragments. Normal C and C++ comments will always remain visible. + +STRIP_CODE_COMMENTS = YES + +# If the REFERENCED_BY_RELATION tag is set to YES +# then for each documented function all documented +# functions referencing it will be listed. + +REFERENCED_BY_RELATION = NO + +# If the REFERENCES_RELATION tag is set to YES +# then for each documented function all documented entities +# called/used by that function will be listed. + +REFERENCES_RELATION = NO + +# If the REFERENCES_LINK_SOURCE tag is set to YES (the default) +# and SOURCE_BROWSER tag is set to YES, then the hyperlinks from +# functions in REFERENCES_RELATION and REFERENCED_BY_RELATION lists will +# link to the source code. Otherwise they will link to the documentstion. + +REFERENCES_LINK_SOURCE = YES + +# If the USE_HTAGS tag is set to YES then the references to source code +# will point to the HTML generated by the htags(1) tool instead of doxygen +# built-in source browser. The htags tool is part of GNU's global source +# tagging system (see http://www.gnu.org/software/global/global.html). You +# will need version 4.8.6 or higher. + +USE_HTAGS = NO + +# If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen +# will generate a verbatim copy of the header file for each class for +# which an include is specified. Set to NO to disable this. + +VERBATIM_HEADERS = YES + +#--------------------------------------------------------------------------- +# configuration options related to the alphabetical class index +#--------------------------------------------------------------------------- + +# If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index +# of all compounds will be generated. Enable this if the project +# contains a lot of classes, structs, unions or interfaces. + +ALPHABETICAL_INDEX = NO + +# If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then +# the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns +# in which this list will be split (can be a number in the range [1..20]) + +COLS_IN_ALPHA_INDEX = 5 + +# In case all classes in a project start with a common prefix, all +# classes will be put under the same header in the alphabetical index. +# The IGNORE_PREFIX tag can be used to specify one or more prefixes that +# should be ignored while generating the index headers. + +IGNORE_PREFIX = + +#--------------------------------------------------------------------------- +# configuration options related to the HTML output +#--------------------------------------------------------------------------- + +# If the GENERATE_HTML tag is set to YES (the default) Doxygen will +# generate HTML output. + +GENERATE_HTML = YES + +# The HTML_OUTPUT tag is used to specify where the HTML docs will be put. +# If a relative path is entered the value of OUTPUT_DIRECTORY will be +# put in front of it. If left blank `html' will be used as the default path. + +HTML_OUTPUT = html + +# The HTML_FILE_EXTENSION tag can be used to specify the file extension for +# each generated HTML page (for example: .htm,.php,.asp). If it is left blank +# doxygen will generate files with .html extension. + +HTML_FILE_EXTENSION = .html + +# The HTML_HEADER tag can be used to specify a personal HTML header for +# each generated HTML page. If it is left blank doxygen will generate a +# standard header. + +HTML_HEADER = + +# The HTML_FOOTER tag can be used to specify a personal HTML footer for +# each generated HTML page. If it is left blank doxygen will generate a +# standard footer. + +HTML_FOOTER = + +# The HTML_STYLESHEET tag can be used to specify a user-defined cascading +# style sheet that is used by each HTML page. It can be used to +# fine-tune the look of the HTML output. If the tag is left blank doxygen +# will generate a default style sheet. Note that doxygen will try to copy +# the style sheet file to the HTML output directory, so don't put your own +# stylesheet in the HTML output directory as well, or it will be erased! + +HTML_STYLESHEET = + +# If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes, +# files or namespaces will be aligned in HTML using tables. If set to +# NO a bullet list will be used. + +HTML_ALIGN_MEMBERS = YES + +# If the GENERATE_HTMLHELP tag is set to YES, additional index files +# will be generated that can be used as input for tools like the +# Microsoft HTML help workshop to generate a compiled HTML help file (.chm) +# of the generated HTML documentation. + +GENERATE_HTMLHELP = NO + +# If the GENERATE_DOCSET tag is set to YES, additional index files +# will be generated that can be used as input for Apple's Xcode 3 +# integrated development environment, introduced with OSX 10.5 (Leopard). +# To create a documentation set, doxygen will generate a Makefile in the +# HTML output directory. Running make will produce the docset in that +# directory and running "make install" will install the docset in +# ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find +# it at startup. + +GENERATE_DOCSET = NO + +# When GENERATE_DOCSET tag is set to YES, this tag determines the name of the +# feed. A documentation feed provides an umbrella under which multiple +# documentation sets from a single provider (such as a company or product suite) +# can be grouped. + +DOCSET_FEEDNAME = "Doxygen generated docs" + +# When GENERATE_DOCSET tag is set to YES, this tag specifies a string that +# should uniquely identify the documentation set bundle. This should be a +# reverse domain-name style string, e.g. com.mycompany.MyDocSet. Doxygen +# will append .docset to the name. + +DOCSET_BUNDLE_ID = org.doxygen.Project + +# If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML +# documentation will contain sections that can be hidden and shown after the +# page has loaded. For this to work a browser that supports +# JavaScript and DHTML is required (for instance Mozilla 1.0+, Firefox +# Netscape 6.0+, Internet explorer 5.0+, Konqueror, or Safari). + +HTML_DYNAMIC_SECTIONS = NO + +# If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can +# be used to specify the file name of the resulting .chm file. You +# can add a path in front of the file if the result should not be +# written to the html output directory. + +CHM_FILE = + +# If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can +# be used to specify the location (absolute path including file name) of +# the HTML help compiler (hhc.exe). If non-empty doxygen will try to run +# the HTML help compiler on the generated index.hhp. + +HHC_LOCATION = + +# If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag +# controls if a separate .chi index file is generated (YES) or that +# it should be included in the master .chm file (NO). + +GENERATE_CHI = NO + +# If the GENERATE_HTMLHELP tag is set to YES, the CHM_INDEX_ENCODING +# is used to encode HtmlHelp index (hhk), content (hhc) and project file +# content. + +CHM_INDEX_ENCODING = + +# If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag +# controls whether a binary table of contents is generated (YES) or a +# normal table of contents (NO) in the .chm file. + +BINARY_TOC = NO + +# The TOC_EXPAND flag can be set to YES to add extra items for group members +# to the contents of the HTML help documentation and to the tree view. + +TOC_EXPAND = NO + +# The DISABLE_INDEX tag can be used to turn on/off the condensed index at +# top of each HTML page. The value NO (the default) enables the index and +# the value YES disables it. + +DISABLE_INDEX = NO + +# This tag can be used to set the number of enum values (range [1..20]) +# that doxygen will group on one line in the generated HTML documentation. + +ENUM_VALUES_PER_LINE = 4 + +# The GENERATE_TREEVIEW tag is used to specify whether a tree-like index +# structure should be generated to display hierarchical information. +# If the tag value is set to FRAME, a side panel will be generated +# containing a tree-like index structure (just like the one that +# is generated for HTML Help). For this to work a browser that supports +# JavaScript, DHTML, CSS and frames is required (for instance Mozilla 1.0+, +# Netscape 6.0+, Internet explorer 5.0+, or Konqueror). Windows users are +# probably better off using the HTML help feature. Other possible values +# for this tag are: HIERARCHIES, which will generate the Groups, Directories, +# and Class Hiererachy pages using a tree view instead of an ordered list; +# ALL, which combines the behavior of FRAME and HIERARCHIES; and NONE, which +# disables this behavior completely. For backwards compatibility with previous +# releases of Doxygen, the values YES and NO are equivalent to FRAME and NONE +# respectively. + +GENERATE_TREEVIEW = NONE + +# If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be +# used to set the initial width (in pixels) of the frame in which the tree +# is shown. + +TREEVIEW_WIDTH = 250 + +# Use this tag to change the font size of Latex formulas included +# as images in the HTML documentation. The default is 10. Note that +# when you change the font size after a successful doxygen run you need +# to manually remove any form_*.png images from the HTML output directory +# to force them to be regenerated. + +FORMULA_FONTSIZE = 10 + +#--------------------------------------------------------------------------- +# configuration options related to the LaTeX output +#--------------------------------------------------------------------------- + +# If the GENERATE_LATEX tag is set to YES (the default) Doxygen will +# generate Latex output. + +#GENERATE_LATEX = YES +GENERATE_LATEX = no + +# The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put. +# If a relative path is entered the value of OUTPUT_DIRECTORY will be +# put in front of it. If left blank `latex' will be used as the default path. + +LATEX_OUTPUT = latex + +# The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be +# invoked. If left blank `latex' will be used as the default command name. + +LATEX_CMD_NAME = latex + +# The MAKEINDEX_CMD_NAME tag can be used to specify the command name to +# generate index for LaTeX. If left blank `makeindex' will be used as the +# default command name. + +MAKEINDEX_CMD_NAME = makeindex + +# If the COMPACT_LATEX tag is set to YES Doxygen generates more compact +# LaTeX documents. This may be useful for small projects and may help to +# save some trees in general. + +COMPACT_LATEX = NO + +# The PAPER_TYPE tag can be used to set the paper type that is used +# by the printer. Possible values are: a4, a4wide, letter, legal and +# executive. If left blank a4wide will be used. + +PAPER_TYPE = a4wide + +# The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX +# packages that should be included in the LaTeX output. + +EXTRA_PACKAGES = + +# The LATEX_HEADER tag can be used to specify a personal LaTeX header for +# the generated latex document. The header should contain everything until +# the first chapter. If it is left blank doxygen will generate a +# standard header. Notice: only use this tag if you know what you are doing! + +LATEX_HEADER = + +# If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated +# is prepared for conversion to pdf (using ps2pdf). The pdf file will +# contain links (just like the HTML output) instead of page references +# This makes the output suitable for online browsing using a pdf viewer. + +PDF_HYPERLINKS = YES + +# If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of +# plain latex in the generated Makefile. Set this option to YES to get a +# higher quality PDF documentation. + +USE_PDFLATEX = YES + +# If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode. +# command to the generated LaTeX files. This will instruct LaTeX to keep +# running if errors occur, instead of asking the user for help. +# This option is also used when generating formulas in HTML. + +LATEX_BATCHMODE = NO + +# If LATEX_HIDE_INDICES is set to YES then doxygen will not +# include the index chapters (such as File Index, Compound Index, etc.) +# in the output. + +LATEX_HIDE_INDICES = NO + +#--------------------------------------------------------------------------- +# configuration options related to the RTF output +#--------------------------------------------------------------------------- + +# If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output +# The RTF output is optimized for Word 97 and may not look very pretty with +# other RTF readers or editors. + +GENERATE_RTF = NO + +# The RTF_OUTPUT tag is used to specify where the RTF docs will be put. +# If a relative path is entered the value of OUTPUT_DIRECTORY will be +# put in front of it. If left blank `rtf' will be used as the default path. + +RTF_OUTPUT = rtf + +# If the COMPACT_RTF tag is set to YES Doxygen generates more compact +# RTF documents. This may be useful for small projects and may help to +# save some trees in general. + +COMPACT_RTF = NO + +# If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated +# will contain hyperlink fields. The RTF file will +# contain links (just like the HTML output) instead of page references. +# This makes the output suitable for online browsing using WORD or other +# programs which support those fields. +# Note: wordpad (write) and others do not support links. + +RTF_HYPERLINKS = NO + +# Load stylesheet definitions from file. Syntax is similar to doxygen's +# config file, i.e. a series of assignments. You only have to provide +# replacements, missing definitions are set to their default value. + +RTF_STYLESHEET_FILE = + +# Set optional variables used in the generation of an rtf document. +# Syntax is similar to doxygen's config file. + +RTF_EXTENSIONS_FILE = + +#--------------------------------------------------------------------------- +# configuration options related to the man page output +#--------------------------------------------------------------------------- + +# If the GENERATE_MAN tag is set to YES (the default) Doxygen will +# generate man pages + +GENERATE_MAN = NO + +# The MAN_OUTPUT tag is used to specify where the man pages will be put. +# If a relative path is entered the value of OUTPUT_DIRECTORY will be +# put in front of it. If left blank `man' will be used as the default path. + +MAN_OUTPUT = man + +# The MAN_EXTENSION tag determines the extension that is added to +# the generated man pages (default is the subroutine's section .3) + +MAN_EXTENSION = .3 + +# If the MAN_LINKS tag is set to YES and Doxygen generates man output, +# then it will generate one additional man file for each entity +# documented in the real man page(s). These additional files +# only source the real man page, but without them the man command +# would be unable to find the correct page. The default is NO. + +MAN_LINKS = NO + +#--------------------------------------------------------------------------- +# configuration options related to the XML output +#--------------------------------------------------------------------------- + +# If the GENERATE_XML tag is set to YES Doxygen will +# generate an XML file that captures the structure of +# the code including all documentation. + +GENERATE_XML = NO + +# The XML_OUTPUT tag is used to specify where the XML pages will be put. +# If a relative path is entered the value of OUTPUT_DIRECTORY will be +# put in front of it. If left blank `xml' will be used as the default path. + +XML_OUTPUT = xml + +# The XML_SCHEMA tag can be used to specify an XML schema, +# which can be used by a validating XML parser to check the +# syntax of the XML files. + +XML_SCHEMA = + +# The XML_DTD tag can be used to specify an XML DTD, +# which can be used by a validating XML parser to check the +# syntax of the XML files. + +XML_DTD = + +# If the XML_PROGRAMLISTING tag is set to YES Doxygen will +# dump the program listings (including syntax highlighting +# and cross-referencing information) to the XML output. Note that +# enabling this will significantly increase the size of the XML output. + +XML_PROGRAMLISTING = YES + +#--------------------------------------------------------------------------- +# configuration options for the AutoGen Definitions output +#--------------------------------------------------------------------------- + +# If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will +# generate an AutoGen Definitions (see autogen.sf.net) file +# that captures the structure of the code including all +# documentation. Note that this feature is still experimental +# and incomplete at the moment. + +GENERATE_AUTOGEN_DEF = NO + +#--------------------------------------------------------------------------- +# configuration options related to the Perl module output +#--------------------------------------------------------------------------- + +# If the GENERATE_PERLMOD tag is set to YES Doxygen will +# generate a Perl module file that captures the structure of +# the code including all documentation. Note that this +# feature is still experimental and incomplete at the +# moment. + +GENERATE_PERLMOD = NO + +# If the PERLMOD_LATEX tag is set to YES Doxygen will generate +# the necessary Makefile rules, Perl scripts and LaTeX code to be able +# to generate PDF and DVI output from the Perl module output. + +PERLMOD_LATEX = NO + +# If the PERLMOD_PRETTY tag is set to YES the Perl module output will be +# nicely formatted so it can be parsed by a human reader. This is useful +# if you want to understand what is going on. On the other hand, if this +# tag is set to NO the size of the Perl module output will be much smaller +# and Perl will parse it just the same. + +PERLMOD_PRETTY = YES + +# The names of the make variables in the generated doxyrules.make file +# are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX. +# This is useful so different doxyrules.make files included by the same +# Makefile don't overwrite each other's variables. + +PERLMOD_MAKEVAR_PREFIX = + +#--------------------------------------------------------------------------- +# Configuration options related to the preprocessor +#--------------------------------------------------------------------------- + +# If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will +# evaluate all C-preprocessor directives found in the sources and include +# files. + +ENABLE_PREPROCESSING = YES + +# If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro +# names in the source code. If set to NO (the default) only conditional +# compilation will be performed. Macro expansion can be done in a controlled +# way by setting EXPAND_ONLY_PREDEF to YES. + +MACRO_EXPANSION = NO + +# If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES +# then the macro expansion is limited to the macros specified with the +# PREDEFINED and EXPAND_AS_DEFINED tags. + +EXPAND_ONLY_PREDEF = NO + +# If the SEARCH_INCLUDES tag is set to YES (the default) the includes files +# in the INCLUDE_PATH (see below) will be search if a #include is found. + +SEARCH_INCLUDES = YES + +# The INCLUDE_PATH tag can be used to specify one or more directories that +# contain include files that are not input files but should be processed by +# the preprocessor. + +INCLUDE_PATH = + +# You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard +# patterns (like *.h and *.hpp) to filter out the header-files in the +# directories. If left blank, the patterns specified with FILE_PATTERNS will +# be used. + +INCLUDE_FILE_PATTERNS = + +# The PREDEFINED tag can be used to specify one or more macro names that +# are defined before the preprocessor is started (similar to the -D option of +# gcc). The argument of the tag is a list of macros of the form: name +# or name=definition (no spaces). If the definition and the = are +# omitted =1 is assumed. To prevent a macro definition from being +# undefined via #undef or recursively expanded use the := operator +# instead of the = operator. + +PREDEFINED = + +# If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then +# this tag can be used to specify a list of macro names that should be expanded. +# The macro definition that is found in the sources will be used. +# Use the PREDEFINED tag if you want to use a different macro definition. + +EXPAND_AS_DEFINED = + +# If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then +# doxygen's preprocessor will remove all function-like macros that are alone +# on a line, have an all uppercase name, and do not end with a semicolon. Such +# function macros are typically used for boiler-plate code, and will confuse +# the parser if not removed. + +SKIP_FUNCTION_MACROS = YES + +#--------------------------------------------------------------------------- +# Configuration::additions related to external references +#--------------------------------------------------------------------------- + +# The TAGFILES option can be used to specify one or more tagfiles. +# Optionally an initial location of the external documentation +# can be added for each tagfile. The format of a tag file without +# this location is as follows: +# TAGFILES = file1 file2 ... +# Adding location for the tag files is done as follows: +# TAGFILES = file1=loc1 "file2 = loc2" ... +# where "loc1" and "loc2" can be relative or absolute paths or +# URLs. If a location is present for each tag, the installdox tool +# does not have to be run to correct the links. +# Note that each tag file must have a unique name +# (where the name does NOT include the path) +# If a tag file is not located in the directory in which doxygen +# is run, you must also specify the path to the tagfile here. + +TAGFILES = + +# When a file name is specified after GENERATE_TAGFILE, doxygen will create +# a tag file that is based on the input files it reads. + +GENERATE_TAGFILE = + +# If the ALLEXTERNALS tag is set to YES all external classes will be listed +# in the class index. If set to NO only the inherited external classes +# will be listed. + +ALLEXTERNALS = NO + +# If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed +# in the modules index. If set to NO, only the current project's groups will +# be listed. + +EXTERNAL_GROUPS = YES + +# The PERL_PATH should be the absolute path and name of the perl script +# interpreter (i.e. the result of `which perl'). + +PERL_PATH = /usr/bin/perl + +#--------------------------------------------------------------------------- +# Configuration options related to the dot tool +#--------------------------------------------------------------------------- + +# If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will +# generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base +# or super classes. Setting the tag to NO turns the diagrams off. Note that +# this option is superseded by the HAVE_DOT option below. This is only a +# fallback. It is recommended to install and use dot, since it yields more +# powerful graphs. + +CLASS_DIAGRAMS = YES + +# You can define message sequence charts within doxygen comments using the \msc +# command. Doxygen will then run the mscgen tool (see +# http://www.mcternan.me.uk/mscgen/) to produce the chart and insert it in the +# documentation. The MSCGEN_PATH tag allows you to specify the directory where +# the mscgen tool resides. If left empty the tool is assumed to be found in the +# default search path. + +MSCGEN_PATH = + +# If set to YES, the inheritance and collaboration graphs will hide +# inheritance and usage relations if the target is undocumented +# or is not a class. + +HIDE_UNDOC_RELATIONS = YES + +# If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is +# available from the path. This tool is part of Graphviz, a graph visualization +# toolkit from AT&T and Lucent Bell Labs. The other options in this section +# have no effect if this option is set to NO (the default) + +HAVE_DOT = NO + +# By default doxygen will write a font called FreeSans.ttf to the output +# directory and reference it in all dot files that doxygen generates. This +# font does not include all possible unicode characters however, so when you need +# these (or just want a differently looking font) you can specify the font name +# using DOT_FONTNAME. You need need to make sure dot is able to find the font, +# which can be done by putting it in a standard location or by setting the +# DOTFONTPATH environment variable or by setting DOT_FONTPATH to the directory +# containing the font. + +DOT_FONTNAME = FreeSans + +# By default doxygen will tell dot to use the output directory to look for the +# FreeSans.ttf font (which doxygen will put there itself). If you specify a +# different font using DOT_FONTNAME you can set the path where dot +# can find it using this tag. + +DOT_FONTPATH = + +# If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen +# will generate a graph for each documented class showing the direct and +# indirect inheritance relations. Setting this tag to YES will force the +# the CLASS_DIAGRAMS tag to NO. + +CLASS_GRAPH = YES + +# If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen +# will generate a graph for each documented class showing the direct and +# indirect implementation dependencies (inheritance, containment, and +# class references variables) of the class with other documented classes. + +COLLABORATION_GRAPH = YES + +# If the GROUP_GRAPHS and HAVE_DOT tags are set to YES then doxygen +# will generate a graph for groups, showing the direct groups dependencies + +GROUP_GRAPHS = YES + +# If the UML_LOOK tag is set to YES doxygen will generate inheritance and +# collaboration diagrams in a style similar to the OMG's Unified Modeling +# Language. + +UML_LOOK = NO + +# If set to YES, the inheritance and collaboration graphs will show the +# relations between templates and their instances. + +TEMPLATE_RELATIONS = NO + +# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT +# tags are set to YES then doxygen will generate a graph for each documented +# file showing the direct and indirect include dependencies of the file with +# other documented files. + +INCLUDE_GRAPH = YES + +# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and +# HAVE_DOT tags are set to YES then doxygen will generate a graph for each +# documented header file showing the documented files that directly or +# indirectly include this file. + +INCLUDED_BY_GRAPH = YES + +# If the CALL_GRAPH and HAVE_DOT options are set to YES then +# doxygen will generate a call dependency graph for every global function +# or class method. Note that enabling this option will significantly increase +# the time of a run. So in most cases it will be better to enable call graphs +# for selected functions only using the \callgraph command. + +CALL_GRAPH = NO + +# If the CALLER_GRAPH and HAVE_DOT tags are set to YES then +# doxygen will generate a caller dependency graph for every global function +# or class method. Note that enabling this option will significantly increase +# the time of a run. So in most cases it will be better to enable caller +# graphs for selected functions only using the \callergraph command. + +CALLER_GRAPH = NO + +# If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen +# will graphical hierarchy of all classes instead of a textual one. + +GRAPHICAL_HIERARCHY = YES + +# If the DIRECTORY_GRAPH, SHOW_DIRECTORIES and HAVE_DOT tags are set to YES +# then doxygen will show the dependencies a directory has on other directories +# in a graphical way. The dependency relations are determined by the #include +# relations between the files in the directories. + +DIRECTORY_GRAPH = YES + +# The DOT_IMAGE_FORMAT tag can be used to set the image format of the images +# generated by dot. Possible values are png, jpg, or gif +# If left blank png will be used. + +DOT_IMAGE_FORMAT = png + +# The tag DOT_PATH can be used to specify the path where the dot tool can be +# found. If left blank, it is assumed the dot tool can be found in the path. + +DOT_PATH = + +# The DOTFILE_DIRS tag can be used to specify one or more directories that +# contain dot files that are included in the documentation (see the +# \dotfile command). + +DOTFILE_DIRS = + +# The DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of +# nodes that will be shown in the graph. If the number of nodes in a graph +# becomes larger than this value, doxygen will truncate the graph, which is +# visualized by representing a node as a red box. Note that doxygen if the +# number of direct children of the root node in a graph is already larger than +# DOT_GRAPH_MAX_NODES then the graph will not be shown at all. Also note +# that the size of a graph can be further restricted by MAX_DOT_GRAPH_DEPTH. + +DOT_GRAPH_MAX_NODES = 50 + +# The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the +# graphs generated by dot. A depth value of 3 means that only nodes reachable +# from the root by following a path via at most 3 edges will be shown. Nodes +# that lay further from the root node will be omitted. Note that setting this +# option to 1 or 2 may greatly reduce the computation time needed for large +# code bases. Also note that the size of a graph can be further restricted by +# DOT_GRAPH_MAX_NODES. Using a depth of 0 means no depth restriction. + +MAX_DOT_GRAPH_DEPTH = 0 + +# Set the DOT_TRANSPARENT tag to YES to generate images with a transparent +# background. This is enabled by default, which results in a transparent +# background. Warning: Depending on the platform used, enabling this option +# may lead to badly anti-aliased labels on the edges of a graph (i.e. they +# become hard to read). + +DOT_TRANSPARENT = YES + +# Set the DOT_MULTI_TARGETS tag to YES allow dot to generate multiple output +# files in one run (i.e. multiple -o and -T options on the command line). This +# makes dot run faster, but since only newer versions of dot (>1.8.10) +# support this, this feature is disabled by default. + +DOT_MULTI_TARGETS = NO + +# If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will +# generate a legend page explaining the meaning of the various boxes and +# arrows in the dot generated graphs. + +GENERATE_LEGEND = YES + +# If the DOT_CLEANUP tag is set to YES (the default) Doxygen will +# remove the intermediate dot files that are used to generate +# the various graphs. + +DOT_CLEANUP = YES + +#--------------------------------------------------------------------------- +# Configuration::additions related to the search engine +#--------------------------------------------------------------------------- + +# The SEARCHENGINE tag specifies whether or not a search engine should be +# used. If set to NO the values of all tags below this one will be ignored. + +SEARCHENGINE = NO diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/php/animals.php b/Master/texmf-dist/doc/support/lua2dox/examples/php/animals.php new file mode 100644 index 00000000000..d7e092e68e4 --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/examples/php/animals.php @@ -0,0 +1,100 @@ +setKind('animal'); + } + function setKind($Kind){ //! \brief set kind of object + $this->kind = $Kind; + } + function call(){ //! \brief say the call of this animal + $speigel = $this->speigel; + if (isset($speigel)) + $speigel = ' says "' . $speigel . '"'; + else + $speigel = ' '; + + TIO_writeln($this->kind . $speigel); + } + +}; + +//! \brief an abstract bird +class Bird extends Animal{ + function Bird(){ //! \brief constructor + $this->setKind('bird'); + } +}; + +//! \brief a subclassed bird +class Pigeon extends Bird{ + function Pigeon(){ //! \brief constructor + $this->setKind('pigeon'); + $this->speigel = 'oh my poor toe Betty'; + } +}; + +//! \brief another subclassed bird +class RedKite extends Bird{ + function RedKite(){ //! \brief constructor + $this->setKind('red kite'); + $this->speigel = 'weee-ooo ee oo ee oo ee oo'; + } +}; + +//! \brief a base mammal +class Mammal extends Animal{ +}; + +//! \brief a subclassed mammal +class Cat extends Mammal{ + function Cat(){ //! \brief constructor + $this->setKind('cat'); + $this->speigel = 'meow'; + } +}; + +//! \brief another subclassed mammal +class Dog extends Mammal{ + function Dog(){ //! \brief constructor + $this->setKind('dog'); + $this->speigel = 'woof'; + } +}; + +//eof +?> \ No newline at end of file diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/animals_8php-source.html b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/animals_8php-source.html new file mode 100644 index 00000000000..0b09c6c0f9b --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/animals_8php-source.html @@ -0,0 +1,104 @@ + + +Sample Code (PHP): animals.php Source File + + + + + +
Generated on Mon Jun 11 16:12:42 2012 for Sample Code (PHP) by  + +doxygen 1.5.6
+ + diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/animals_8php.html b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/animals_8php.html new file mode 100644 index 00000000000..e67ed03f772 --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/animals_8php.html @@ -0,0 +1,113 @@ + + +Sample Code (PHP): animals.php File Reference + + + + + +
+

animals.php File Reference

test some classes More... +

+ +

+Go to the source code of this file. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

Classes

class  Animal
 a base class More...
class  Bird
 an abstract bird More...
class  Cat
 a subclassed mammal More...
class  Dog
 another subclassed mammal More...
class  Mammal
 a base mammal More...
class  Pigeon
 a subclassed bird More...
class  RedKite
 another subclassed bird More...

Functions

 TIO_write ($Str)
 write to stdout
 TIO_writeln ($Str)
 writeln to stdout
+


Detailed Description

+test some classes +

+Here we make some animals +

Definition in file animals.php.

+

Function Documentation

+ +
+
+ + + + + + + + + +
TIO_write ( Str  ) 
+
+
+ +

+write to stdout +

+ +

Definition at line 25 of file animals.php.

+ +
+

+ +

+
+ + + + + + + + + +
TIO_writeln ( Str  ) 
+
+
+ +

+writeln to stdout +

+ +

Definition at line 31 of file animals.php.

+ +
+

+

+
Generated on Mon Jun 11 16:12:42 2012 for Sample Code (PHP) by  + +doxygen 1.5.6
+ + diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/annotated.html b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/annotated.html new file mode 100644 index 00000000000..d4d8e985916 --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/annotated.html @@ -0,0 +1,39 @@ + + +Sample Code (PHP): Class List + + + + + +
+

Class List

Here are the classes, structs, unions and interfaces with brief descriptions: + + + + + + + +
AnimalBase class
BirdAbstract bird
CatSubclassed mammal
DogAnother subclassed mammal
MammalBase mammal
PigeonSubclassed bird
RedKiteAnother subclassed bird
+
+
Generated on Mon Jun 11 16:12:42 2012 for Sample Code (PHP) by  + +doxygen 1.5.6
+ + diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classAnimal-members.html b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classAnimal-members.html new file mode 100644 index 00000000000..f18c16bfd9a --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classAnimal-members.html @@ -0,0 +1,34 @@ + + +Sample Code (PHP): Member List + + + + + +
+

Animal Member List

This is the complete list of members for Animal, including all inherited members.

+ + + +
Animal()Animal
call()Animal
setKind($Kind)Animal

+
Generated on Mon Jun 11 16:12:42 2012 for Sample Code (PHP) by  + +doxygen 1.5.6
+ + diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classAnimal.html b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classAnimal.html new file mode 100644 index 00000000000..8240b7617d8 --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classAnimal.html @@ -0,0 +1,135 @@ + + +Sample Code (PHP): Animal Class Reference + + + + + +
+

Animal Class Reference

a base class +More... +

+

+Inheritance diagram for Animal:
+
+ +

+ +Bird +Mammal +Pigeon +RedKite +Cat +Dog + +
+ +

+List of all members. + + + + + + + + +

Public Member Functions

 Animal ()
 call ()
 setKind ($Kind)
+


Detailed Description

+a base class +

Definition at line 37 of file animals.php.

+

Member Function Documentation

+ +
+
+ + + + + + + + +
Animal::Animal (  ) 
+
+
+ +

+ +

+constructor +

Definition at line 38 of file animals.php.

+ +
+

+ +

+
+ + + + + + + + +
Animal::call (  ) 
+
+
+ +

+ +

+say the call of this animal +

Definition at line 44 of file animals.php.

+ +
+

+ +

+
+ + + + + + + + + +
Animal::setKind ( Kind  ) 
+
+
+ +

+ +

+set kind of object +

Definition at line 41 of file animals.php.

+ +
+

+


The documentation for this class was generated from the following file: +
+
Generated on Mon Jun 11 16:12:42 2012 for Sample Code (PHP) by  + +doxygen 1.5.6
+ + diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classAnimal.png b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classAnimal.png new file mode 100644 index 00000000000..796bc999ca1 Binary files /dev/null and b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classAnimal.png differ diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classBird-members.html b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classBird-members.html new file mode 100644 index 00000000000..494846b0c14 --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classBird-members.html @@ -0,0 +1,35 @@ + + +Sample Code (PHP): Member List + + + + + +
+

Bird Member List

This is the complete list of members for Bird, including all inherited members.

+ + + + +
Animal()Animal
Bird()Bird
call()Animal
setKind($Kind)Animal

+
Generated on Mon Jun 11 16:12:42 2012 for Sample Code (PHP) by  + +doxygen 1.5.6
+ + diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classBird.html b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classBird.html new file mode 100644 index 00000000000..d07da26aad3 --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classBird.html @@ -0,0 +1,81 @@ + + +Sample Code (PHP): Bird Class Reference + + + + + +
+

Bird Class Reference

an abstract bird +More... +

+

+Inheritance diagram for Bird:
+
+ +

+ +Animal +Pigeon +RedKite + +
+ +

+List of all members. + + + + +

Public Member Functions

 Bird ()
+


Detailed Description

+an abstract bird +

Definition at line 57 of file animals.php.

+

Member Function Documentation

+ +
+
+ + + + + + + + +
Bird::Bird (  ) 
+
+
+ +

+ +

+constructor +

Definition at line 58 of file animals.php.

+ +
+

+


The documentation for this class was generated from the following file: +
+
Generated on Mon Jun 11 16:12:42 2012 for Sample Code (PHP) by  + +doxygen 1.5.6
+ + diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classBird.png b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classBird.png new file mode 100644 index 00000000000..d63f59dba48 Binary files /dev/null and b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classBird.png differ diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classCat-members.html b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classCat-members.html new file mode 100644 index 00000000000..d1db7e4ae8b --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classCat-members.html @@ -0,0 +1,35 @@ + + +Sample Code (PHP): Member List + + + + + +
+

Cat Member List

This is the complete list of members for Cat, including all inherited members.

+ + + + +
Animal()Animal
call()Animal
Cat()Cat
setKind($Kind)Animal

+
Generated on Mon Jun 11 16:12:42 2012 for Sample Code (PHP) by  + +doxygen 1.5.6
+ + diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classCat.html b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classCat.html new file mode 100644 index 00000000000..b5be89fa275 --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classCat.html @@ -0,0 +1,80 @@ + + +Sample Code (PHP): Cat Class Reference + + + + + +
+

Cat Class Reference

a subclassed mammal +More... +

+

+Inheritance diagram for Cat:
+
+ +

+ +Mammal +Animal + +
+ +

+List of all members. + + + + +

Public Member Functions

 Cat ()
+


Detailed Description

+a subclassed mammal +

Definition at line 84 of file animals.php.

+

Member Function Documentation

+ +
+
+ + + + + + + + +
Cat::Cat (  ) 
+
+
+ +

+ +

+constructor +

Definition at line 85 of file animals.php.

+ +
+

+


The documentation for this class was generated from the following file: +
+
Generated on Mon Jun 11 16:12:42 2012 for Sample Code (PHP) by  + +doxygen 1.5.6
+ + diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classCat.png b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classCat.png new file mode 100644 index 00000000000..8500fb0b00a Binary files /dev/null and b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classCat.png differ diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classDog-members.html b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classDog-members.html new file mode 100644 index 00000000000..19c1dd7aa51 --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classDog-members.html @@ -0,0 +1,35 @@ + + +Sample Code (PHP): Member List + + + + + +
+

Dog Member List

This is the complete list of members for Dog, including all inherited members.

+ + + + +
Animal()Animal
call()Animal
Dog()Dog
setKind($Kind)Animal

+
Generated on Mon Jun 11 16:12:42 2012 for Sample Code (PHP) by  + +doxygen 1.5.6
+ + diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classDog.html b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classDog.html new file mode 100644 index 00000000000..76846557a37 --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classDog.html @@ -0,0 +1,80 @@ + + +Sample Code (PHP): Dog Class Reference + + + + + +
+

Dog Class Reference

another subclassed mammal +More... +

+

+Inheritance diagram for Dog:
+
+ +

+ +Mammal +Animal + +
+ +

+List of all members. + + + + +

Public Member Functions

 Dog ()
+


Detailed Description

+another subclassed mammal +

Definition at line 92 of file animals.php.

+

Member Function Documentation

+ +
+
+ + + + + + + + +
Dog::Dog (  ) 
+
+
+ +

+ +

+constructor +

Definition at line 93 of file animals.php.

+ +
+

+


The documentation for this class was generated from the following file: +
+
Generated on Mon Jun 11 16:12:42 2012 for Sample Code (PHP) by  + +doxygen 1.5.6
+ + diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classDog.png b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classDog.png new file mode 100644 index 00000000000..6ba62396a49 Binary files /dev/null and b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classDog.png differ diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classMammal-members.html b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classMammal-members.html new file mode 100644 index 00000000000..23d9d6e96ba --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classMammal-members.html @@ -0,0 +1,34 @@ + + +Sample Code (PHP): Member List + + + + + +
+

Mammal Member List

This is the complete list of members for Mammal, including all inherited members.

+ + + +
Animal()Animal
call()Animal
setKind($Kind)Animal

+
Generated on Mon Jun 11 16:12:42 2012 for Sample Code (PHP) by  + +doxygen 1.5.6
+ + diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classMammal.html b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classMammal.html new file mode 100644 index 00000000000..9157b98a02d --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classMammal.html @@ -0,0 +1,54 @@ + + +Sample Code (PHP): Mammal Class Reference + + + + + +
+

Mammal Class Reference

a base mammal +More... +

+

+Inheritance diagram for Mammal:
+
+ +

+ +Animal +Cat +Dog + +
+ +

+List of all members. + +
+


Detailed Description

+a base mammal +

Definition at line 80 of file animals.php.

+
The documentation for this class was generated from the following file: +
+
Generated on Mon Jun 11 16:12:42 2012 for Sample Code (PHP) by  + +doxygen 1.5.6
+ + diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classMammal.png b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classMammal.png new file mode 100644 index 00000000000..a736bde5a35 Binary files /dev/null and b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classMammal.png differ diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classPigeon-members.html b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classPigeon-members.html new file mode 100644 index 00000000000..38490e8d13f --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classPigeon-members.html @@ -0,0 +1,36 @@ + + +Sample Code (PHP): Member List + + + + + +
+

Pigeon Member List

This is the complete list of members for Pigeon, including all inherited members.

+ + + + + +
Animal()Animal
Bird()Bird
call()Animal
Pigeon()Pigeon
setKind($Kind)Animal

+
Generated on Mon Jun 11 16:12:42 2012 for Sample Code (PHP) by  + +doxygen 1.5.6
+ + diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classPigeon.html b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classPigeon.html new file mode 100644 index 00000000000..3c5736ca013 --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classPigeon.html @@ -0,0 +1,80 @@ + + +Sample Code (PHP): Pigeon Class Reference + + + + + +
+

Pigeon Class Reference

a subclassed bird +More... +

+

+Inheritance diagram for Pigeon:
+
+ +

+ +Bird +Animal + +
+ +

+List of all members. + + + + +

Public Member Functions

 Pigeon ()
+


Detailed Description

+a subclassed bird +

Definition at line 64 of file animals.php.

+

Member Function Documentation

+ +
+
+ + + + + + + + +
Pigeon::Pigeon (  ) 
+
+
+ +

+ +

+constructor +

Definition at line 65 of file animals.php.

+ +
+

+


The documentation for this class was generated from the following file: +
+
Generated on Mon Jun 11 16:12:42 2012 for Sample Code (PHP) by  + +doxygen 1.5.6
+ + diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classPigeon.png b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classPigeon.png new file mode 100644 index 00000000000..dc73930253a Binary files /dev/null and b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classPigeon.png differ diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classRedKite-members.html b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classRedKite-members.html new file mode 100644 index 00000000000..ecde52536ac --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classRedKite-members.html @@ -0,0 +1,36 @@ + + +Sample Code (PHP): Member List + + + + + +
+

RedKite Member List

This is the complete list of members for RedKite, including all inherited members.

+ + + + + +
Animal()Animal
Bird()Bird
call()Animal
RedKite()RedKite
setKind($Kind)Animal

+
Generated on Mon Jun 11 16:12:42 2012 for Sample Code (PHP) by  + +doxygen 1.5.6
+ + diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classRedKite.html b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classRedKite.html new file mode 100644 index 00000000000..b02adb50d2a --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classRedKite.html @@ -0,0 +1,80 @@ + + +Sample Code (PHP): RedKite Class Reference + + + + + +
+

RedKite Class Reference

another subclassed bird +More... +

+

+Inheritance diagram for RedKite:
+
+ +

+ +Bird +Animal + +
+ +

+List of all members. + + + + +

Public Member Functions

 RedKite ()
+


Detailed Description

+another subclassed bird +

Definition at line 72 of file animals.php.

+

Member Function Documentation

+ +
+
+ + + + + + + + +
RedKite::RedKite (  ) 
+
+
+ +

+ +

+constructor +

Definition at line 73 of file animals.php.

+ +
+

+


The documentation for this class was generated from the following file: +
+
Generated on Mon Jun 11 16:12:42 2012 for Sample Code (PHP) by  + +doxygen 1.5.6
+ + diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classRedKite.png b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classRedKite.png new file mode 100644 index 00000000000..b286f8c415a Binary files /dev/null and b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/classRedKite.png differ diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/doxygen.css b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/doxygen.css new file mode 100644 index 00000000000..22c484301dd --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/doxygen.css @@ -0,0 +1,473 @@ +BODY,H1,H2,H3,H4,H5,H6,P,CENTER,TD,TH,UL,DL,DIV { + font-family: Geneva, Arial, Helvetica, sans-serif; +} +BODY,TD { + font-size: 90%; +} +H1 { + text-align: center; + font-size: 160%; +} +H2 { + font-size: 120%; +} +H3 { + font-size: 100%; +} +CAPTION { + font-weight: bold +} +DIV.qindex { + width: 100%; + background-color: #e8eef2; + border: 1px solid #84b0c7; + text-align: center; + margin: 2px; + padding: 2px; + line-height: 140%; +} +DIV.navpath { + width: 100%; + background-color: #e8eef2; + border: 1px solid #84b0c7; + text-align: center; + margin: 2px; + padding: 2px; + line-height: 140%; +} +DIV.navtab { + background-color: #e8eef2; + border: 1px solid #84b0c7; + text-align: center; + margin: 2px; + margin-right: 15px; + padding: 2px; +} +TD.navtab { + font-size: 70%; +} +A.qindex { + text-decoration: none; + font-weight: bold; + color: #1A419D; +} +A.qindex:visited { + text-decoration: none; + font-weight: bold; + color: #1A419D +} +A.qindex:hover { + text-decoration: none; + background-color: #ddddff; +} +A.qindexHL { + text-decoration: none; + font-weight: bold; + background-color: #6666cc; + color: #ffffff; + border: 1px double #9295C2; +} +A.qindexHL:hover { + text-decoration: none; + background-color: #6666cc; + color: #ffffff; +} +A.qindexHL:visited { + text-decoration: none; + background-color: #6666cc; + color: #ffffff +} +A.el { + text-decoration: none; + font-weight: bold +} +A.elRef { + font-weight: bold +} +A.code:link { + text-decoration: none; + font-weight: normal; + color: #0000FF +} +A.code:visited { + text-decoration: none; + font-weight: normal; + color: #0000FF +} +A.codeRef:link { + font-weight: normal; + color: #0000FF +} +A.codeRef:visited { + font-weight: normal; + color: #0000FF +} +A:hover { + text-decoration: none; + background-color: #f2f2ff +} +DL.el { + margin-left: -1cm +} +.fragment { + font-family: monospace, fixed; + font-size: 95%; +} +PRE.fragment { + border: 1px solid #CCCCCC; + background-color: #f5f5f5; + margin-top: 4px; + margin-bottom: 4px; + margin-left: 2px; + margin-right: 8px; + padding-left: 6px; + padding-right: 6px; + padding-top: 4px; + padding-bottom: 4px; +} +DIV.ah { + background-color: black; + font-weight: bold; + color: #ffffff; + margin-bottom: 3px; + margin-top: 3px +} + +DIV.groupHeader { + margin-left: 16px; + margin-top: 12px; + margin-bottom: 6px; + font-weight: bold; +} +DIV.groupText { + margin-left: 16px; + font-style: italic; + font-size: 90% +} +BODY { + background: white; + color: black; + margin-right: 20px; + margin-left: 20px; +} +TD.indexkey { + background-color: #e8eef2; + font-weight: bold; + padding-right : 10px; + padding-top : 2px; + padding-left : 10px; + padding-bottom : 2px; + margin-left : 0px; + margin-right : 0px; + margin-top : 2px; + margin-bottom : 2px; + border: 1px solid #CCCCCC; +} +TD.indexvalue { + background-color: #e8eef2; + font-style: italic; + padding-right : 10px; + padding-top : 2px; + padding-left : 10px; + padding-bottom : 2px; + margin-left : 0px; + margin-right : 0px; + margin-top : 2px; + margin-bottom : 2px; + border: 1px solid #CCCCCC; +} +TR.memlist { + background-color: #f0f0f0; +} +P.formulaDsp { + text-align: center; +} +IMG.formulaDsp { +} +IMG.formulaInl { + vertical-align: middle; +} +SPAN.keyword { color: #008000 } +SPAN.keywordtype { color: #604020 } +SPAN.keywordflow { color: #e08000 } +SPAN.comment { color: #800000 } +SPAN.preprocessor { color: #806020 } +SPAN.stringliteral { color: #002080 } +SPAN.charliteral { color: #008080 } +SPAN.vhdldigit { color: #ff00ff } +SPAN.vhdlchar { color: #000000 } +SPAN.vhdlkeyword { color: #700070 } +SPAN.vhdllogic { color: #ff0000 } + +.mdescLeft { + padding: 0px 8px 4px 8px; + font-size: 80%; + font-style: italic; + background-color: #FAFAFA; + border-top: 1px none #E0E0E0; + border-right: 1px none #E0E0E0; + border-bottom: 1px none #E0E0E0; + border-left: 1px none #E0E0E0; + margin: 0px; +} +.mdescRight { + padding: 0px 8px 4px 8px; + font-size: 80%; + font-style: italic; + background-color: #FAFAFA; + border-top: 1px none #E0E0E0; + border-right: 1px none #E0E0E0; + border-bottom: 1px none #E0E0E0; + border-left: 1px none #E0E0E0; + margin: 0px; +} +.memItemLeft { + padding: 1px 0px 0px 8px; + margin: 4px; + border-top-width: 1px; + border-right-width: 1px; + border-bottom-width: 1px; + border-left-width: 1px; + border-top-color: #E0E0E0; + border-right-color: #E0E0E0; + border-bottom-color: #E0E0E0; + border-left-color: #E0E0E0; + border-top-style: solid; + border-right-style: none; + border-bottom-style: none; + border-left-style: none; + background-color: #FAFAFA; + font-size: 80%; +} +.memItemRight { + padding: 1px 8px 0px 8px; + margin: 4px; + border-top-width: 1px; + border-right-width: 1px; + border-bottom-width: 1px; + border-left-width: 1px; + border-top-color: #E0E0E0; + border-right-color: #E0E0E0; + border-bottom-color: #E0E0E0; + border-left-color: #E0E0E0; + border-top-style: solid; + border-right-style: none; + border-bottom-style: none; + border-left-style: none; + background-color: #FAFAFA; + font-size: 80%; +} +.memTemplItemLeft { + padding: 1px 0px 0px 8px; + margin: 4px; + border-top-width: 1px; + border-right-width: 1px; + border-bottom-width: 1px; + border-left-width: 1px; + border-top-color: #E0E0E0; + border-right-color: #E0E0E0; + border-bottom-color: #E0E0E0; + border-left-color: #E0E0E0; + border-top-style: none; + border-right-style: none; + border-bottom-style: none; + border-left-style: none; + background-color: #FAFAFA; + font-size: 80%; +} +.memTemplItemRight { + padding: 1px 8px 0px 8px; + margin: 4px; + border-top-width: 1px; + border-right-width: 1px; + border-bottom-width: 1px; + border-left-width: 1px; + border-top-color: #E0E0E0; + border-right-color: #E0E0E0; + border-bottom-color: #E0E0E0; + border-left-color: #E0E0E0; + border-top-style: none; + border-right-style: none; + border-bottom-style: none; + border-left-style: none; + background-color: #FAFAFA; + font-size: 80%; +} +.memTemplParams { + padding: 1px 0px 0px 8px; + margin: 4px; + border-top-width: 1px; + border-right-width: 1px; + border-bottom-width: 1px; + border-left-width: 1px; + border-top-color: #E0E0E0; + border-right-color: #E0E0E0; + border-bottom-color: #E0E0E0; + border-left-color: #E0E0E0; + border-top-style: solid; + border-right-style: none; + border-bottom-style: none; + border-left-style: none; + color: #606060; + background-color: #FAFAFA; + font-size: 80%; +} +.search { + color: #003399; + font-weight: bold; +} +FORM.search { + margin-bottom: 0px; + margin-top: 0px; +} +INPUT.search { + font-size: 75%; + color: #000080; + font-weight: normal; + background-color: #e8eef2; +} +TD.tiny { + font-size: 75%; +} +a { + color: #1A41A8; +} +a:visited { + color: #2A3798; +} +.dirtab { + padding: 4px; + border-collapse: collapse; + border: 1px solid #84b0c7; +} +TH.dirtab { + background: #e8eef2; + font-weight: bold; +} +HR { + height: 1px; + border: none; + border-top: 1px solid black; +} + +/* Style for detailed member documentation */ +.memtemplate { + font-size: 80%; + color: #606060; + font-weight: normal; + margin-left: 3px; +} +.memnav { + background-color: #e8eef2; + border: 1px solid #84b0c7; + text-align: center; + margin: 2px; + margin-right: 15px; + padding: 2px; +} +.memitem { + padding: 4px; + background-color: #eef3f5; + border-width: 1px; + border-style: solid; + border-color: #dedeee; + -moz-border-radius: 8px 8px 8px 8px; +} +.memname { + white-space: nowrap; + font-weight: bold; +} +.memdoc{ + padding-left: 10px; +} +.memproto { + background-color: #d5e1e8; + width: 100%; + border-width: 1px; + border-style: solid; + border-color: #84b0c7; + font-weight: bold; + -moz-border-radius: 8px 8px 8px 8px; +} +.paramkey { + text-align: right; +} +.paramtype { + white-space: nowrap; +} +.paramname { + color: #602020; + font-style: italic; + white-space: nowrap; +} +/* End Styling for detailed member documentation */ + +/* for the tree view */ +.ftvtree { + font-family: sans-serif; + margin:0.5em; +} +/* these are for tree view when used as main index */ +.directory { + font-size: 9pt; + font-weight: bold; +} +.directory h3 { + margin: 0px; + margin-top: 1em; + font-size: 11pt; +} + +/* The following two styles can be used to replace the root node title */ +/* with an image of your choice. Simply uncomment the next two styles, */ +/* specify the name of your image and be sure to set 'height' to the */ +/* proper pixel height of your image. */ + +/* .directory h3.swap { */ +/* height: 61px; */ +/* background-repeat: no-repeat; */ +/* background-image: url("yourimage.gif"); */ +/* } */ +/* .directory h3.swap span { */ +/* display: none; */ +/* } */ + +.directory > h3 { + margin-top: 0; +} +.directory p { + margin: 0px; + white-space: nowrap; +} +.directory div { + display: none; + margin: 0px; +} +.directory img { + vertical-align: -30%; +} +/* these are for tree view when not used as main index */ +.directory-alt { + font-size: 100%; + font-weight: bold; +} +.directory-alt h3 { + margin: 0px; + margin-top: 1em; + font-size: 11pt; +} +.directory-alt > h3 { + margin-top: 0; +} +.directory-alt p { + margin: 0px; + white-space: nowrap; +} +.directory-alt div { + display: none; + margin: 0px; +} +.directory-alt img { + vertical-align: -30%; +} + diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/doxygen.png b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/doxygen.png new file mode 100644 index 00000000000..f0a274bbaff Binary files /dev/null and b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/doxygen.png differ diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/files.html b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/files.html new file mode 100644 index 00000000000..18f4a3a2eeb --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/files.html @@ -0,0 +1,33 @@ + + +Sample Code (PHP): File Index + + + + + +
+

File List

Here is a list of all files with brief descriptions: + + +
animals.php [code]Test some classes
main.php [code]Test code
+
+
Generated on Mon Jun 11 16:12:42 2012 for Sample Code (PHP) by  + +doxygen 1.5.6
+ + diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/functions.html b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/functions.html new file mode 100644 index 00000000000..7b4b6c2c833 --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/functions.html @@ -0,0 +1,56 @@ + + +Sample Code (PHP): Class Members + + + + + +
+Here is a list of all class members with links to the classes they belong to: +

+

+
+
Generated on Mon Jun 11 16:12:42 2012 for Sample Code (PHP) by  + +doxygen 1.5.6
+ + diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/functions_func.html b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/functions_func.html new file mode 100644 index 00000000000..6537f326f75 --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/functions_func.html @@ -0,0 +1,56 @@ + + +Sample Code (PHP): Class Members - Functions + + + + + +
+  +

+

+
+
Generated on Mon Jun 11 16:12:42 2012 for Sample Code (PHP) by  + +doxygen 1.5.6
+ + diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/globals.html b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/globals.html new file mode 100644 index 00000000000..87db63ef6f8 --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/globals.html @@ -0,0 +1,46 @@ + + +Sample Code (PHP): Class Members + + + + + +
+Here is a list of all file members with links to the files they belong to: +

+

+
+
Generated on Mon Jun 11 16:12:42 2012 for Sample Code (PHP) by  + +doxygen 1.5.6
+ + diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/globals_func.html b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/globals_func.html new file mode 100644 index 00000000000..81d0332ca5e --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/globals_func.html @@ -0,0 +1,44 @@ + + +Sample Code (PHP): Class Members + + + + + +
+  +

+

+
+
Generated on Mon Jun 11 16:12:42 2012 for Sample Code (PHP) by  + +doxygen 1.5.6
+ + diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/globals_vars.html b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/globals_vars.html new file mode 100644 index 00000000000..0324b884be4 --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/globals_vars.html @@ -0,0 +1,42 @@ + + +Sample Code (PHP): Class Members + + + + + +
+  +

+

+
+
Generated on Mon Jun 11 16:12:42 2012 for Sample Code (PHP) by  + +doxygen 1.5.6
+ + diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/hierarchy.html b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/hierarchy.html new file mode 100644 index 00000000000..4ef8cc5e7ec --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/hierarchy.html @@ -0,0 +1,45 @@ + + +Sample Code (PHP): Hierarchical Index + + + + + +
+

Class Hierarchy

This inheritance list is sorted roughly, but not completely, alphabetically: +
+
Generated on Mon Jun 11 16:12:42 2012 for Sample Code (PHP) by  + +doxygen 1.5.6
+ + diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/index.html b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/index.html new file mode 100644 index 00000000000..3d19a414b0a --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/index.html @@ -0,0 +1,25 @@ + + +Sample Code (PHP): Main Page + + + + + +
+

Sample Code (PHP) Documentation

+

+

0.1 20120518

Some test code. This shows a hierachy of classes. For this example we do animals.
+
Generated on Mon Jun 11 16:12:42 2012 for Sample Code (PHP) by  + +doxygen 1.5.6
+ + diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/main_8php-source.html b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/main_8php-source.html new file mode 100644 index 00000000000..b3a4c2057a1 --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/main_8php-source.html @@ -0,0 +1,51 @@ + + +Sample Code (PHP): main.php Source File + + + + + +
Generated on Mon Jun 11 16:12:42 2012 for Sample Code (PHP) by  + +doxygen 1.5.6
+ + diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/main_8php.html b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/main_8php.html new file mode 100644 index 00000000000..ac67cb9550b --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/main_8php.html @@ -0,0 +1,63 @@ + + +Sample Code (PHP): main.php File Reference + + + + + +
+

main.php File Reference

test code More... +

+ +

+Go to the source code of this file. + + + + +

Variables

 $animals
+


Detailed Description

+test code +

+ +

Definition in file main.php.

+

Variable Documentation

+ +
+
+ + + + +
$animals
+
+
+ +

+Initial value:

 array(
+   new Cat
+  ,new Dog
+  ,new Bird
+  ,new RedKite
+  ,new Pigeon
+  )
+
+

Definition at line 32 of file main.php.

+ +
+

+

+
Generated on Mon Jun 11 16:12:42 2012 for Sample Code (PHP) by  + +doxygen 1.5.6
+ + diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/tab_b.gif b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/tab_b.gif new file mode 100644 index 00000000000..0d623483ffd Binary files /dev/null and b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/tab_b.gif differ diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/tab_l.gif b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/tab_l.gif new file mode 100644 index 00000000000..9b1e6337c92 Binary files /dev/null and b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/tab_l.gif differ diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/tab_r.gif b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/tab_r.gif new file mode 100644 index 00000000000..ce9dd9f533c Binary files /dev/null and b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/tab_r.gif differ diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/tabs.css b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/tabs.css new file mode 100644 index 00000000000..95f00a91da3 --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/examples/php/docs/html/tabs.css @@ -0,0 +1,102 @@ +/* tabs styles, based on http://www.alistapart.com/articles/slidingdoors */ + +DIV.tabs +{ + float : left; + width : 100%; + background : url("tab_b.gif") repeat-x bottom; + margin-bottom : 4px; +} + +DIV.tabs UL +{ + margin : 0px; + padding-left : 10px; + list-style : none; +} + +DIV.tabs LI, DIV.tabs FORM +{ + display : inline; + margin : 0px; + padding : 0px; +} + +DIV.tabs FORM +{ + float : right; +} + +DIV.tabs A +{ + float : left; + background : url("tab_r.gif") no-repeat right top; + border-bottom : 1px solid #84B0C7; + font-size : x-small; + font-weight : bold; + text-decoration : none; +} + +DIV.tabs A:hover +{ + background-position: 100% -150px; +} + +DIV.tabs A:link, DIV.tabs A:visited, +DIV.tabs A:active, DIV.tabs A:hover +{ + color: #1A419D; +} + +DIV.tabs SPAN +{ + float : left; + display : block; + background : url("tab_l.gif") no-repeat left top; + padding : 5px 9px; + white-space : nowrap; +} + +DIV.tabs INPUT +{ + float : right; + display : inline; + font-size : 1em; +} + +DIV.tabs TD +{ + font-size : x-small; + font-weight : bold; + text-decoration : none; +} + + + +/* Commented Backslash Hack hides rule from IE5-Mac \*/ +DIV.tabs SPAN {float : none;} +/* End IE5-Mac hack */ + +DIV.tabs A:hover SPAN +{ + background-position: 0% -150px; +} + +DIV.tabs LI.current A +{ + background-position: 100% -150px; + border-width : 0px; +} + +DIV.tabs LI.current SPAN +{ + background-position: 0% -150px; + padding-bottom : 6px; +} + +DIV.navpath +{ + background : none; + border : none; + border-bottom : 1px solid #84B0C7; +} diff --git a/Master/texmf-dist/doc/support/lua2dox/examples/php/main.php b/Master/texmf-dist/doc/support/lua2dox/examples/php/main.php new file mode 100644 index 00000000000..dc806d7e088 --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/examples/php/main.php @@ -0,0 +1,44 @@ +call(); + +//eof +?> \ No newline at end of file diff --git a/Master/texmf-dist/doc/support/lua2dox/install.sh b/Master/texmf-dist/doc/support/lua2dox/install.sh new file mode 100755 index 00000000000..7d6cda7be15 --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/install.sh @@ -0,0 +1,73 @@ +#!/bin/sh + +########################################################################### +# Copyright (C) 2012 by Simon Dales # +# simon@purrsoft.co.uk # +# # +# This program is free software; you can redistribute it and/or modify # +# it under the terms of the GNU General Public License as published by # +# the Free Software Foundation; either version 2 of the License, or # +# (at your option) any later version. # +# # +# This program is distributed in the hope that it will be useful, # +# but WITHOUT ANY WARRANTY; without even the implied warranty of # +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # +# GNU General Public License for more details. # +# # +# You should have received a copy of the GNU General Public License # +# along with this program; if not, write to the # +# Free Software Foundation, Inc., # +# 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. # +########################################################################### + +INSTALLDIR="$1" +#################### +HOME="/home/${USER}" +DEFAULT_INSTALLDIR="${HOME}/bin" + +if test -z "${INSTALLDIR}" +then + INSTALLDIR="${DEFAULT_INSTALLDIR}" +fi + +APP_NAME="lua2dox_lua" +############################ +go_splat(){ + echo "ERROR!: $1" + exit 1 + } + +mk_link(){ + echo "mk \"$1\" -> \"$2\"" + ln -s "$1" "$2" || go_splat "creating link: \"$1\" -> \"$2\"" + } + +do_install(){ + echo "install to \"${INSTALLDIR}\"" + + CURRENT_DIR=`pwd` + APP_PATH="${CURRENT_DIR}/${APP_NAME}" + echo "app path=\"${APP_PATH}\"" + cd "${INSTALLDIR}" + + mk_link "${APP_PATH}" "lua2dox_lua" + mk_link "${APP_PATH}" "lua2dox_filter" + + echo "install done." + } + +## main +case "${INSTALLDIR}" in +--help) + echo "Syntax:" + echo "$0 |" + echo "" + echo "--help show this help" + echo " install directory for links" + echo "default =\"~/bin\"" + ;; +*) +do_install + ;; +esac +##eof \ No newline at end of file diff --git a/Master/texmf-dist/doc/support/lua2dox/lua2dox-refm.pdf b/Master/texmf-dist/doc/support/lua2dox/lua2dox-refm.pdf new file mode 100644 index 00000000000..2b0b81e2cea Binary files /dev/null and b/Master/texmf-dist/doc/support/lua2dox/lua2dox-refm.pdf differ diff --git a/Master/texmf-dist/doc/support/lua2dox/lua2dox-refm.tex b/Master/texmf-dist/doc/support/lua2dox/lua2dox-refm.tex new file mode 100644 index 00000000000..dfa42dc5bac --- /dev/null +++ b/Master/texmf-dist/doc/support/lua2dox/lua2dox-refm.tex @@ -0,0 +1,416 @@ +\documentclass[a4paper]{article} +%\nofiles + +\usepackage[T1]{fontenc} +\usepackage{hyperref} +\usepackage{listings} +\input{lua.def} % not installed properly so just include here + +%% +% h +\parindent=0bp +\textwidth=450bp +\oddsidemargin=0bp + +% v +\parskip=.5em +\voffset=-70bp +\textheight=750bp + + +%%%%%%%%%%%%%%%%% +\def\sectionSprout(#1,#2){\vspace{#1}\penalty#2\vspace{-#1}} +\def\Sect{\sectionSprout(125bp,-150)\section} +\def\SSect{\sectionSprout(100bp,-100)\subsection} +\def\SSSect{\sectionSprout(80bp,-50)\subsubsection} + +\def\BT{\begin{tabular}} +\def\ET{\end{tabular}} + +\def\BE{\begin{enumerate}} +\def\EE{\end{enumerate}} +\def\IE{\item } + +\def\BI{\begin{itemize}} +\def\EI{\end{itemize}} +\def\II{\item } + +\long\def\Nerd#1{{\tt #1}} +\def\URL#1{{\tt #1}} +\def\LuaToDoX{Lua2D\raise-.3em\hbox{O}X$_{lua}$} +\def\luatodox{\Nerd{lua2dox\_lua}} +\def\Doxygen{\Nerd{Doxygen}} +\def\doxygen{\Nerd{doxygen}} +\def\To{$\rightarrow$} + +\def\Foot#1{\footnote{#1}} + +\lstset{language=C++ + ,frame=single + ,numbers=left + ,numberstyle=\tiny + ,tabsize=2 + } + +\hypersetup{ + pdfinfo={ + Title={Lua2DoX lua ref manual} + ,Subject={Autodoc tool for Lua} + } + ,colorlinks=true + ,linkcolor=blue + } + +\begin{document} +\pagestyle{empty} +\begin{center} + \huge \LuaToDoX + + \large + v0.1 + + Copyright (c) 2012 Simon Dales + + 4th July 2012 + +{\fboxsep=.5em\fboxrule=.1bp\fbox{% +\begin{minipage}{300bp} +\hyphenpenalty=10000% +\small +%\begin{abstract} +This is a hack to enable \doxygen{} to document lua. + +It uses the well-known \doxygen{} filter mechanism to fool \doxygen{} into reading foreign languages. + +If this works for you then enjoy. + +%\end{abstract} +\end{minipage} +}} +\end{center} + +\tableofcontents + +\newpage +\pagestyle{headings} + +\Sect{Introduction} + +Documenting sourcecode is a hassle. +There are two basic methods of providing documented sourcecode: ``literate programming'' and ``autodoc''. +Without these tools a human has to keep the documentation and code aligned, which rarely happens. + +\SSect{Literate Programming} + +If one is sufficiently organised, and it fits in with your existing work practices, then there is +a lot going for literate programming. +Here you write a combined document that contains both code and documentation fragments. +When you want code or documentation you run it through a program which assembles the appropriate files. + +This is theoretically the neatest way of making code. +The best known example of literate programming is the source of \TeX. + +\SSect{Autodoc} + +In the real world we get source from many sources, usually where literate programming wasn't used or isn't available. + +One solution is to use an automatic documentation tool: +feed it sourcecode and it will extract what documentation it can. + +If you feed it raw source then all it can do is tell you where it found features such as function and class declarations. + +If your source has been suitably prepared, then more detailed documentation can be produced. +This preparation takes the form of ``magic comments''. +These are source comments that contain ``magic'' features that let the autodoc tool know to make use of them. + +\SSSect{Doxygen} + +\Doxygen{} is one of the many autodoc tools use to document C-like languages. +It is widely used and supported in the linux world and has MacOS and Windows ports. + +\begin{lstlisting}[firstnumber=83] +void helloWorldOnce(){ + printf("hello world\n"); + } +/*! + \brief writes hello world *n + + This is a demo of how to loop round + and print something + + \param N number of times round +*/ +void helloWorldN(int N){ + for (int i=0;i +PROJECT_NUMBER = +OUTPUT_DIRECTORY = docs +FILE_PATTERNS = *.lua +FILTER_PATTERNS = *.lua=lua2dox_filter +SOURCE_BROWSER = yes +GENERATE_LATEX = no +\end{lstlisting} + +Either add them to the end or find the appropriate entry in \Nerd{Doxyfile}. + +\SSSect{run \LuaToDoX} + +Once \Nerd{Doxyfile} has been edited run as ``\Nerd{lua2dox\_lua}''. + +When reading source with classes multiple passes are needed. +Each pass generates a list of member functions (as a file) that were found on this pass. +This list is read in on the next pass. +If the class+methods haven't changed this time then you only need to run it once, else run twice, +much like running \LaTeX{} \Nerd{$\backslash$tableofcontents}. + +\SSect{In use} + +As with \doxygen{} the HTML output is the most useful for development. +When the project is finished then PDF output (via \LaTeX) may be useful. + +Typically you will have some source files open in your editor/IDE. +Also keep a web-browser window open pointing at the documentation. + +After a bit of editing the documentation will become stale. +At this point run \LuaToDoX{} once/twice and refresh the HTML pages. +Then your documentation will be updated. + +\newpage +\Sect{Design} + +\LuaToDoX{} is a \doxygen{} filter. +It has a basic parser that will read each line of lua and output an equivalent in pseudo-C++. +It loops round until it has found the end of the file. +It only has to be good enough for \doxygen{} to see it as legal. +Therefore our lua interpreter is fairly limited, but ``good enough''. + +The parser is relatively crude and assumes that the programmer writes lua in a fairly +clean way. +Some bits of lua will confuse it. + +In order for the source browser to work in the \doxygen{} output it must preserve the number of lines. +The output of each line is either written as-is or a converted line. +When \doxygen{} re-reads the source to make the source-HTML/\LaTeX{}/\ldots it uses the line number +to set the position. + + +It only supports comments that preceded the function/class declaration. +Any in the middle will act as cruft in the resulting documentation. +This will be slightly out of place but at least should refer to somewhere near to +where it was intended. +In particular ``\Nerd{@todo}''. This will appear in the ToDo list, but not associated with the right function. + +\SSect{Classes} +Class declarations are assumed to be using a ``well-known'' userdefined function ``\Nerd{class()}''. +It processes\goodbreak``\Nerd{AA = class(A)}'' \To{} ``\Nerd{class AA: public A\{\}};''. + +However it will probably have some member functions. +These get converted from \goodbreak''\Nerd{A.foo(a,b)}'' \To{} ``\Nerd{A::foo(a,b)}''. +This is stored in a temporary file. +When \LuaToDoX{} is run a subsequent time this is used to generate a list of methods. +So \goodbreak``\Nerd{AA = class(A)}'' \To{} ``\Nerd{class AA: public A\{foo(a,b);bar(x);\}};'' + + +\SSect{Multiline function declarations} + +Because \LuaToDoX{} can only process one line at a time it cannot correctly process function declarations +with multiline parameter list. +This is because the parser isn't sophisticated enough to guarantee finding the close paren on some random later line. + +So I have put in a hack that will insert the ``missing'' close paren. +It looks at the function declaration that you have got and checks for a close paren. +It if is not there then it will add a spoof parameter and the close. + +The effect is that you will get the function documented, but not with the parameter list you might expect. + +\begin{lstlisting}[firstnumber=94] +function foo(A + ,B + ,C) +\end{lstlisting} + +Becomes +\begin{lstlisting}[firstnumber=94] +function foo(A,___MissingCloseParenHere___) +\end{lstlisting} + +\SSect{Multiple magic comments} + +The hacking of lua to C++ by \LuaToDoX{} has the limitation that some magic comments will not get associated with the correct function/class. This is a ``feature'' that might get correct in a later version. + + +\end{document} + +%%eof \ No newline at end of file diff --git a/Master/texmf-dist/scripts/lua2dox/lua.def b/Master/texmf-dist/scripts/lua2dox/lua.def new file mode 100755 index 00000000000..83af433e61e --- /dev/null +++ b/Master/texmf-dist/scripts/lua2dox/lua.def @@ -0,0 +1,39 @@ +% -*- latex -*- +% Definition of the Lua language for the listings package +% Time-stamp: <2008-11-30 15:27:16 rsmith> +% Written by Roland Smith and hereby placed in the public +% domain. + +\lstdefinelanguage{lua} + {morekeywords={and,break,do,else,elseif,end,false,for,function,if,in,local, + nil,not,or,repeat,return,then,true,until,while}, + morekeywords={[2]arg,assert,collectgarbage,dofile,error,_G,getfenv, + getmetatable,ipairs,load,loadfile,loadstring,next,pairs,pcall,print, + rawequal,rawget,rawset,select,setfenv,setmetatable,tonumber,tostring, + type,unpack,_VERSION,xpcall}, + morekeywords={[2]coroutine.create,coroutine.resume,coroutine.running, + coroutine.status,coroutine.wrap,coroutine.yield}, + morekeywords={[2]module,require,package.cpath,package.load,package.loaded, + package.loaders,package.loadlib,package.path,package.preload, + package.seeall}, + morekeywords={[2]string.byte,string.char,string.dump,string.find, + string.format,string.gmatch,string.gsub,string.len,string.lower, + string.match,string.rep,string.reverse,string.sub,string.upper}, + morekeywords={[2]table.concat,table.insert,table.maxn,table.remove, + table.sort}, + morekeywords={[2]math.abs,math.acos,math.asin,math.atan,math.atan2, + math.ceil,math.cos,math.cosh,math.deg,math.exp,math.floor,math.fmod, + math.frexp,math.huge,math.ldexp,math.log,math.log10,math.max,math.min, + math.modf,math.pi,math.pow,math.rad,math.random,math.randomseed,math.sin, + math.sinh,math.sqrt,math.tan,math.tanh}, + morekeywords={[2]io.close,io.flush,io.input,io.lines,io.open,io.output, + io.popen,io.read,io.tmpfile,io.type,io.write,file:close,file:flush, + file:lines,file:read,file:seek,file:setvbuf,file:write}, + morekeywords={[2]os.clock,os.date,os.difftime,os.execute,os.exit,os.getenv, + os.remove,os.rename,os.setlocale,os.time,os.tmpname}, + sensitive=true, + morecomment=[l]{--}, + morecomment=[s]{--[[}{]]}, + morestring=[b]", + morestring=[d]' + } diff --git a/Master/texmf-dist/scripts/lua2dox/lua2dox.lua b/Master/texmf-dist/scripts/lua2dox/lua2dox.lua new file mode 100755 index 00000000000..9249baac9cd --- /dev/null +++ b/Master/texmf-dist/scripts/lua2dox/lua2dox.lua @@ -0,0 +1,618 @@ +--[[-------------------------------------------------------------------------- + -- Copyright (C) 2012 by Simon Dales -- + -- simon@purrsoft.co.uk -- + -- -- + -- This program is free software; you can redistribute it and/or modify -- + -- it under the terms of the GNU General Public License as published by -- + -- the Free Software Foundation; either version 2 of the License, or -- + -- (at your option) any later version. -- + -- -- + -- This program is distributed in the hope that it will be useful, -- + -- but WITHOUT ANY WARRANTY; without even the implied warranty of -- + -- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the -- + -- GNU General Public License for more details. -- + -- -- + -- You should have received a copy of the GNU General Public License -- + -- along with this program; if not, write to the -- + -- Free Software Foundation, Inc., -- + -- 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. -- +----------------------------------------------------------------------------]] + +--[[! + \file + \brief a hack lua2dox converter + ]] + +--[[! + \mainpage + + + A hack lua2dox converter + Version 0.1 + + This lets us make Doxygen output some documentation to let + us develop this code. + + It is partially cribbed from the functionality of lua2dox + (http://search.cpan.org/~alec/Doxygen-Lua-0.02/lib/Doxygen/Lua.pm). + Found on CPAN when looking for something else; kinda handy. + + Improved from lua2dox to make the doxygen output more friendly. + Also it runs faster in lua rather than Perl. + + Because this Perl based system is called "lua2dox"., I have decided to add ".lua" to the name + to keep the two separate. + + 0. Ensure doxygen is installed on your system and that you are familiar with its use. + Best is to try to make and document some simple C/C++/PHP to see what it produces. + + 1. Run "lua2dox_lua -g" to create a default Doxyfile. + + Then alter it to let it recognise lua. Add the two following lines: + + FILE_PATTERNS = *.lua + + FILTER_PATTERNS = *.lua=lua2dox_filter + + Either add them to the end or find the appropriate entry in Doxyfile. + + 2. When Doxyfile is edited run as "lua2dox_lua" + + When reading source with classes multiple passes are needed. + Each pass generates a list of member functions (as a file) that were found on this pass. + This list is read in on the next pass. + If the class+methods haven't changed this time then you only need to run it once, else run twice. + + The core function reads the input file (filename or stdin) and outputs some pseudo C-ish language. + It only has to be good enough for doxygen to see it as legal. + Therefore our lua interpreter is fairly limited, but "good enough". + + One limitation is that each line is treated separately (except for long comments). + The implication is that class and function declarations must be on the same line. + Some functions can have their parameter lists extended over multiple lines to make it look neat. + Managing this where there are also some comments is a bit more coding than I want to do at this stage, + so it will probably not document accurately if we do do this. + + However I have put in a hack that will insert the "missing" close paren. + The effect is that you will get the function documented, but not with the parameter list you might expect. + + Installation: + + Here for linux or unix-like, for any other OS you need to refer to other documentation. + + This file is "lua2dox.lua". It gets called by "lua2dox_lua". + Somewhere in your path (e.g. "~/bin" or "/usr/local/bin") put two links to "lua2dox_lua". + Names to use are "lua2dox_lua" and "lua2dox_filter". + + Call it as "lua2dox_lua" and the filter that gets called by doxygen is "lua2dox_filter". + + ]] + +-- we won't use our library code, so this becomes more portable + +local TConfig_config={ + ['LUA2DOX_COMMENTARY_FILE_IN']='./killme_lua2dox.methods' + ,['LUA2DOX_COMMENTARY_FILE_OUT']='./killme_lua2dox.methods.out' + } + +--! \brief Gets a config val +local function TConfig_get(Key,Default) + local val = TConfig_config[Key] + if not val then + val = Default + end + return val +end + +--! \brief sets a config val +local function TConfig_set(Key,Val) + TConfig_config[Key] = Val +end + +--! \brief write to stdout +--! +--! writes Str (if not nil) +local function TIO_write(Str) + if (Str) then + io.write(Str) + end +end + +--! \brief write to stdout +--! +--! writelns Str (if not nil) and then an eoln. +local function TIO_writeln(Str) + if (Str) then + io.write(Str) + end + io.write("\n") +end + +--! \brief show error to stdout +--! +--! writelns Str (if not nil) and then an eoln. +local function TIO_showError(Err,Str) + local err = Err + if not err then + err = 1 + end + + TIO_write('Error (' .. err .. '):') + TIO_writeln(Str) + return err +end + +--! \brief run system command +local function TOS_system(Cmd) + local errno,str + local rtn = os.execute(Cmd) + if not (rtn==0) then + errno = rtn + str = 'an error occured' + end + return errno,str +end + +--! \brief does file exist? +local function TOS_fileExists(Filename) + local fh = io.open(Filename,'r') + if fh~=nil then + fh:close() + return true + end + return false +end + +--! \brief get the current time +local function TClock_GetTimeNow() + if os.gettimeofday then + return os.gettimeofday() + else + return os.time() + end +end + +--! \brief get a timestamp +--! +--! not strictly necessary here but lets us put a timestamp on the end of the output stream. +--! Note that doxygen won't read this, and being off the end of the true file length (num lines), +--! it will have no effect. +--! However it lets us check the output file tail when debugging. +--! +local function TClock_getTimeStamp() + local now = TClock_GetTimeNow() + local fraction_secs = now - math.floor(now) + return os.date('%c %Z',now) .. ':' .. fraction_secs +end + +--! \brief trims a string from both ends +local function TString_trim(Str) + return Str:match("^%s*(.-)%s*$") +end + +--! \brief split a string +--! +--! \param Str +--! \param Pattern +--! \returns table of string fragments +local function TString_split(Str, Pattern) + local splitStr = {} + local fpat = "(.-)" .. Pattern + local last_end = 1 + local str, e, cap = string.find(Str,fpat, 1) + while str do + if str ~= 1 or cap ~= "" then + table.insert(splitStr,cap) + end + last_end = e+1 + str, e, cap = string.find(Str,fpat, last_end) + end + if last_end <= #Str then + cap = string.sub(Str,last_end) + table.insert(splitStr, cap) + end + return splitStr +end + +--! \brief trim comment off end of string +--! +--! If the string has a comment on the end, this trims it off. +--! +local function TString_removeCommentFromLine(Line) + local pos_comment = string.find(Line,'%-%-') + if pos_comment then + Line = string.sub(Line,1,pos_comment-1) + end + return Line +end + +local TClassList_methods = {} +--! \brief get methods +local function TClassList_method_get(Klass) + return TClassList_methods[Klass] +end + +--! \brief add a method to list of known methods +local function TClassList_method_add(Klass,Method) + local classRec = TClassList_methods[Klass] + if not classRec then + TClassList_methods[Klass] = {} + classRec = TClassList_methods[Klass] + end + table.insert(classRec,Method) +end + + +local TCommentary_fh + +--! \brief write to output file +local function TCommentary_writeln(Str) + if TCommentary_fh then + TCommentary_fh:write(Str .. '\n') + end +end + +local TCommentary_fileID +--! \brief open the commentary save file +local function TCommentary_open(Filename,InputLuaFilename) + TCommentary_fileID = '"' .. InputLuaFilename .. '" : ' .. TClock_getTimeStamp() + TCommentary_fh = io.open(Filename,'a+') + if TCommentary_fh then + TCommentary_writeln('// opened:' .. TCommentary_fileID) + end +end + +--! \brief close the methods save file +local function TCommentary_close() + if TCommentary_fh then + TCommentary_writeln('// closed: ' .. TCommentary_fileID) + TCommentary_fh:close() + TCommentary_fh = nil + end +end + +--! \brief read stuff from save file +local function TCommentary_readFileContents(Filename) + if TOS_fileExists(Filename) then + local klass,method,dot + local cmd,colon + local k,v,equals + for line in io.lines(Filename) do + if string.sub(line,1,2)=='//' then + -- it's a comment + else + colon = string.find(line,':') + if colon then + cmd = string.sub(line,1,colon) + line = string.sub(line,colon+1) + else + cmd = nil + end + if (cmd == 'method:') then + dot = string.find(line,'%.') + klass = string.sub(line,1,dot-1) + method = string.sub(line,dot+1) + TClassList_method_add(klass,method) + elseif(cmd == 'set:') then + equals = string.find(line,'=') + if equals then + k = string.sub(line,1,equals-1) + v = string.sub(line,equals+1) + TConfig_set(k,v) + else + TConfig_set(line,true) + end + else -- ignore + TIO_write('/* bad command:"' .. line .. '" */') + end + end + end + else + TIO_write('/* file "' .. Filename .. '" don\'t exist */') + end +end + +--! \brief method to save file +local function TCommentary_addMethod(Klass,Method) + if TCommentary_fh then + if Klass and Method then + if string.find(Klass,'%.') or string.find(Method,'%.') then + -- iffy, so we discard it + else + TCommentary_writeln('method:' .. Klass .. '.' .. Method) + end + end + end +end + +--! \brief output line to stream +--! +--! Wraps IO_writeln() +local function TIO_out2stream(Line) + TIO_writeln(Line) +end + +--! \brief suppress line +local function TIO_out2stream_commented(Line,Prefix,Suffix) + local line = Line + if (not Prefix) then + Prefix='' + end + line = Prefix .. ':' .. line + + if (Suffix) then + line = line .. Suffix + end + TIO_out2stream('// D' .. line) +end + + +TCommandline_argv = {} +--! \brief setup/parse the commandline +local function TCommandline_setup() + local argv1 =arg[1] + if not argv1 then + argv1 = 'base' + end + TCommandline_argv_appname = argv1 + + local i=2 + local argvi=1 + while (argvi) do + argvi = arg[i] + if argvi then + TCommandline_argv[i-1] = argvi + i = i + 1 + end + end +end +--! setup the commandline now +TCommandline_setup() + +--! \brief get commandline args +local function TCommandline_getargv() + return TCommandline_argv +end + +--! \brief get appname +local function TApp_get_appname() + return TCommandline_argv_appname +end + +--! \brief hack converter from lua to a pseudoC-ish language for doxygen +--! +--! This is a hack to make lua readable to doxygen. +--! +--! It works well enough to document functions/methods and classes, but not assignments. +--! Our pseudo-C gets confused if we allow assginments to be shown. +--! Because these are less interesting than class/functions/methods I have decided to +--! live with this limitation. +--! +local function TApp_lua2dox(FileContents) + local err + local lines = FileContents + local maxi=#lines + + local i = 1 + local line,head + while not err and (i<=maxi) do + line = TString_trim(lines[i]) + if #line==0 then + TIO_out2stream() + elseif string.sub(line,1,2)=='--' then + -- it's a comment of some kind + if string.sub(line,1,3)=='--!' then + -- it's a magic comment + TIO_out2stream('//!' .. string.sub(line,4)) + elseif string.sub(line,1,4)=='--[[' then + -- it's a multiline comment + -- read lines to end of comment + local hitend + local comment = '' + line = string.sub(line,5) --.. sep + while not err and (i0) then + line = line .. ' :public ' .. parent + end + + -- need methods list + local methods = TClassList_method_get(klass) + local methods_str + if methods then + methods_str = 'public: ' + for k,v in pairs(methods) do + methods_str = methods_str .. v .. ';' + end + else + methods_str = '/* no methods reported */' + end + line = line .. '{' .. methods_str .. '}' + + TIO_out2stream(line .. ';',true) + else + -- we don't know what this line means, so we can probably just comment it out + TIO_out2stream_commented(line) + end + + i = i + 1 + end + return err +end + +--! \brief run the filter +--! +--! \param AppTimestamp application + timestamp for this run +--! \param Filename the filename or if nil stdin +--! \param CommentaryFiles names of commentary files +--! \return err or nil +--! +local function TApp_run_filter(AppTimestamp,Filename,CommentaryFiles) + local err + local filecontents + if Filename then + -- syphon lines to our table + filecontents={} + for line in io.lines(Filename) do + table.insert(filecontents,line) + end + else + -- get stuff from stdin as a long string (with crlfs etc) + filecontents=io.read('*a') + -- make it a table of lines + filecontents = TString_split(filecontents,'[\n]') -- note this only works for unix files. + Filename = 'stdin' + end + + if filecontents then + TCommentary_readFileContents(CommentaryFiles.infile) + TCommentary_open(CommentaryFiles.outfile,Filename) + + err = TApp_lua2dox(filecontents) + + TCommentary_close() + + TIO_writeln('// done (' .. AppTimestamp .. ')') + else + err = TIO_showError(1,'couldn\'t find any file contents') + end + return err +end + +--! \brief run doxygen for one +--! +--! \param AppTimestamp application + timestamp for this run +--! \param Argv commandline for this run +--! \param CommentaryFiles names of commentary files +--! \return err or nil +--! +local function TApp_run_doxygen(AppTimestamp,Argv,CommentaryFiles) + local err + TIO_writeln('running: ' .. AppTimestamp) + + local argv1 = Argv[1] + if argv1=='--help' then + local appname = TApp_get_appname() + TIO_writeln('Syntax:') + TIO_writeln(' ' .. appname .. ' [[-g] [-s]] []|--help') + TIO_writeln(' --help show this text') + TIO_writeln(' -g: generate new Doxyfile') + TIO_writeln(' -s: generate new Doxyfile without comments') + TIO_writeln(' : name of Doxyfile') + + TIO_writeln() + TIO_writeln(' For help on doxygen run its help system directly') + --! \todo more help here + else + local cl = 'doxygen' + for i,argv_i in ipairs(Argv) do + if i>=1 then -- don't want to use this app's name + cl = cl .. ' ' .. argv_i + end + end + + TIO_writeln('about to run "' .. cl .. '"') + err = TOS_system(cl) + + if not err then + -- cycle commentary files + local newComments=CommentaryFiles.outfile + local nextRunsComments=CommentaryFiles.infile + if TOS_fileExists(newComments) then + TIO_writeln('found outfile "' .. newComments .. '"') + os.remove(nextRunsComments) + TIO_writeln('mv "' .. newComments .. '"-> ' .. nextRunsComments .. '"') + os.rename(newComments,nextRunsComments) + end + end + end + return err +end + +-- main +local timestamp = TClock_getTimeStamp() +local appname = TApp_get_appname() +local version = '0.1 20120704' +local appTimestamp = appname .. '(v' .. version .. ') :' .. timestamp +local commentary_files = { + infile=TConfig_get('LUA2DOX_COMMENTARY_FILE_IN') + ,outfile=TConfig_get('LUA2DOX_COMMENTARY_FILE_OUT') + } + +if appname == 'lua2dox_filter' then + err = TApp_run_filter(appTimestamp,TCommandline_getargv()[1],commentary_files) + TIO_writeln('// do filter') +else + err = TApp_run_doxygen(appTimestamp,TCommandline_getargv(),commentary_files) +end + +--eof \ No newline at end of file diff --git a/Master/texmf-dist/scripts/lua2dox/lua2dox_lua b/Master/texmf-dist/scripts/lua2dox/lua2dox_lua new file mode 100755 index 00000000000..822fed7bea1 --- /dev/null +++ b/Master/texmf-dist/scripts/lua2dox/lua2dox_lua @@ -0,0 +1,86 @@ +#!/bin/bash + +########################################################################### +# Copyright (C) 2012 by Simon Dales # +# simon@purrsoft.co.uk # +# # +# This program is free software; you can redistribute it and/or modify # +# it under the terms of the GNU General Public License as published by # +# the Free Software Foundation; either version 2 of the License, or # +# (at your option) any later version. # +# # +# This program is distributed in the hope that it will be useful, # +# but WITHOUT ANY WARRANTY; without even the implied warranty of # +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # +# GNU General Public License for more details. # +# # +# You should have received a copy of the GNU General Public License # +# along with this program; if not, write to the # +# Free Software Foundation, Inc., # +# 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. # +########################################################################### + +##! \brief test executable to see if it exists +test_executable(){ + P_EXE="$1" + ######### + WHICH=`which ${P_EXE}` + if test -z "${WHICH}" + then + echo "not found \"${P_EXE}\"" + else + EXE="${P_EXE}" + fi + } + +##! \brief sets the lua interpreter +set_lua(){ + test_executable 'texlua' + if test -z "${EXE}" + then + test_executable 'lua' + fi + #echo "final EXE=\"${EXE}\"" + } + +##! \brief makes canonical name of file +##! +##! Note that "readlink -f" doesn't work in MacOSX +##! +do_readlink(){ + pushd . > /dev/null + TARGET_FILE=$1 + + cd `dirname $TARGET_FILE` + TARGET_FILE=`basename $TARGET_FILE` + + # Iterate down a (possible) chain of symlinks + while [ -L "$TARGET_FILE" ] + do + TARGET_FILE=`readlink $TARGET_FILE` + cd `dirname $TARGET_FILE` + TARGET_FILE=`basename $TARGET_FILE` + done + + PHYS_DIR=`pwd -P` + RESULT=$PHYS_DIR + popd > /dev/null + } + +##main +set_lua +if test -z "${EXE}" +then + echo "no lua interpreter available" +else + BASENAME=`basename "$0"` + do_readlink "$0" + DIRNAME="${RESULT}" + + LUASCRIPT="${DIRNAME}/lua2dox.lua ${BASENAME}" + #echo "lua[${LUASCRIPT}]" + + ${EXE} ${LUASCRIPT} $@ +fi +# +##eof \ No newline at end of file diff --git a/Master/tlpkg/bin/tlpkg-ctan-check b/Master/tlpkg/bin/tlpkg-ctan-check index 5f5d0877ac4..3db13c59fbf 100755 --- a/Master/tlpkg/bin/tlpkg-ctan-check +++ b/Master/tlpkg/bin/tlpkg-ctan-check @@ -248,7 +248,8 @@ my @TLP_working = qw( lshort-slovenian lshort-spanish lshort-thai lshort-turkish lshort-ukr lshort-vietnamese lstaddons ltabptch ltxdockit ltxindex ltxkeys ltxmisc ltxnew ltxtools - lua-alt-getopt lua-check-hyphen lua-visual-debug luabibentry luacode + lua-alt-getopt lua-check-hyphen lua-visual-debug + lua2dox luabibentry luacode luaindex luainputenc lualatex-doc lualatex-math lualibs luamplib luaotfload luapersian luasseq luatexbase luatexja luatextra lxfonts ly1 diff --git a/Master/tlpkg/libexec/ctan2tds b/Master/tlpkg/libexec/ctan2tds index 0c20d0d8c34..d49e7e7174d 100755 --- a/Master/tlpkg/libexec/ctan2tds +++ b/Master/tlpkg/libexec/ctan2tds @@ -1293,6 +1293,7 @@ $standardtex='\.(.bx|cfg|sty|clo|ldf|cls|def|fd|cmap|4ht)$'; 'logic', 'milstd\.tex|' . $standardtex, 'ltxkeys', '\.sty|\.clo|\.ldf|\.cls|\.def|\.fd$', # not cfg 'lua-visual-debug', '\.lua|' . $standardtex, + 'lua2dox', 'NULL', # .def is lua code 'lualatex-math', '\.sty', # not phst-doc.cls 'magyar', 'NULL', # do not install in runtime, conflicts with babel 'manjutex', '\.sty|\.clo|\.ldf|\.cls|\.def|\.fd$|manju.tex', @@ -1564,6 +1565,7 @@ $standardtex='\.(.bx|cfg|sty|clo|ldf|cls|def|fd|cmap|4ht)$'; 'lh', 'fonts', 'latex-notes-zh-cn', 'generic', 'lua-alt-getopt', 'support', + 'lua2dox', 'support', 'luatexja', 'luatex', 'marvosym', 'fonts', 'mathabx', 'fonts', @@ -2161,6 +2163,7 @@ $standardxmt='\.xmt'; %specialscripts_nobin = ( 'epspdf' => '(epspdf(|\.help|boot|tk)|\.rb|makegray\.pro)$', 'lua-alt-getopt' => '\.lua$', + 'lua2dox' => '\.(lua|def)$', 'luaindex' => '\.lua$', 'lualatex-math' => '\.lua$', 'luasseq' => '\.lua$', @@ -2196,6 +2199,7 @@ $standardxmt='\.xmt'; 'latexpand' => 'latexpand$', 'listbib' => 'listbib$', 'listings-ext' => '\.sh$', + 'lua2dox' => 'lua2dox_lua$', # doscripts() does _filter 'match_parens' => '^match_parens$', 'mathspic' => '^mathspic\.pl$', 'mf2pt1' => '\.pl$', @@ -2836,42 +2840,44 @@ sub dotype1{ # scripts. Make them executable even if it isn't always necessary. # Build/source/tex/texlive/linked_scripts/Makefile.am installs symlinks # in the bin directories where needed. That Makefile is independently -# maintained, needs to be updated by hand when new user-visible scripts +# maintained, and needs to be updated by hand when new user-visible scripts # are added. We add/update the script itself under linked_scripts. # We also make the symlinks/w32-wrapper-copy in Master/bin. # sub doscripts { my $pwd = getcwd(); - # first do the ones that don't go in the bindirs. - my $scriptpatt = $specialscripts_nobin{$package}; + my $build_tldir = "texk/texlive"; + my $build_scriptsdir = "$build_tldir/linked_scripts"; + my $builddir = "$BUILDDEST/$build_scriptsdir/$package"; + + # first do the user-visible bindir entries. + $scriptpatt = $specialscripts_bin{$package}; if ($scriptpatt) { if ($pwd ne "$DEST/scripts/$package") { # in the .tds.zip case, we will already be in the scripts dir. &install ("$DEST/scripts/$package", $scriptpatt); &SYSTEM ("chmod a+x $DEST/scripts/$package/*"); } - } - # now the user-visible bindir entries. Duplicating above, sorry. - $scriptpatt = $specialscripts_bin{$package}; - return unless $scriptpatt; + # update the copy in Build (the reason we do the bindir ones first). + &xmkdir ($builddir); + &SYSTEM ("$CP $DEST/scripts/$package/* $builddir/"); + } - if ($pwd ne "$DEST/scripts/$package") { - # in the .tds.zip case, we will already be in the scripts dir. - &install ("$DEST/scripts/$package", $scriptpatt); - &SYSTEM ("chmod a+x $DEST/scripts/$package/*"); + # then do the ones that go only under scripts/ and not in the bindirs. + my $nobin_scriptpatt = $specialscripts_nobin{$package}; + if ($nobin_scriptpatt) { + if ($pwd ne "$DEST/scripts/$package") { + # in the .tds.zip case, we will already be in the scripts dir. + &install ("$DEST/scripts/$package", $nobin_scriptpatt); + &SYSTEM ("chmod a+x $DEST/scripts/$package/*"); + } } - # update the copy in Build, too. - my $build_tldir = "texk/texlive"; - my $build_scriptsdir = "$build_tldir/linked_scripts"; - my $builddir = "$BUILDDEST/$build_scriptsdir/$package"; - &xmkdir ($builddir); - &SYSTEM ("$CP $DEST/scripts/$package/* $builddir/"); - - # List of scripts we're installing. + # List of scripts we just copied in for installing in the bindirs. chomp (my @scripts = `cd $builddir && ls`); + return unless @scripts; # For each, give a warning if missing from the Makefile.am in the sources. # Also, if not already present, create the platform-specific bindir entries. @@ -2892,13 +2898,18 @@ sub doscripts { if ($p ne "win32") { my $linktarget = "../../$DEST_TREE/scripts/$package/$s"; &SYSTEM ("ln -s $linktarget $platdir/$linkname"); + # + # Scripts with special cases. &SYSTEM ("ln -s $linkname $platdir/r$linkname") if $linkname =~ /pdfcrop|epstopdf/; # rpdfcrop -> pdfcrop + &SYSTEM ("ln -s $linkname $platdir/lua2dox_filter") + if $linkname =~ /lua2dox_lua/; } else { # Windows. If a shell script, skip. Else copy the wrapper. - next if $s =~ /\.sh$/; + next if $s =~ /\.sh$|lua2dox/; my $w32_wrapper = "$Build/$build_tldir/w32_wrapper/runscript.exe"; &SYSTEM ("$CP $w32_wrapper $platdir/$linkname.exe"); + # &SYSTEM ("$CP $w32_wrapper $platdir/r$linkname.exe") if $linkname =~ /pdfcrop|epstopdf/; # rpdfcrop.exe } diff --git a/Master/tlpkg/tlpsrc/collection-luatex.tlpsrc b/Master/tlpkg/tlpsrc/collection-luatex.tlpsrc index 8c565a37a4f..ddaf405f81d 100644 --- a/Master/tlpkg/tlpsrc/collection-luatex.tlpsrc +++ b/Master/tlpkg/tlpsrc/collection-luatex.tlpsrc @@ -9,6 +9,7 @@ depend checkcites depend chickenize depend interpreter depend lua-visual-debug +depend lua2dox depend luabibentry depend luacode depend luaindex diff --git a/Master/tlpkg/tlpsrc/lua2dox.tlpsrc b/Master/tlpkg/tlpsrc/lua2dox.tlpsrc new file mode 100644 index 00000000000..9a845a9d030 --- /dev/null +++ b/Master/tlpkg/tlpsrc/lua2dox.tlpsrc @@ -0,0 +1,2 @@ +binpattern f bin/${ARCH}/lua2dox_lua +binpattern f bin/${ARCH}/lua2dox_filter -- cgit v1.2.3