| /external/python/cpython2/Doc/library/ |
| D | docxmlrpcserver.rst | 18 :mod:`SimpleXMLRPCServer` to serve HTML documentation in response to HTTP GET
38 POST requests, documentation GET requests, and modifies logging so that the
52 HTML documentation. This allows a server to provide its own web-based
53 documentation.
58 Set the title used in the generated HTML documentation. This title will be used
64 Set the name used in the generated HTML documentation. This name will appear at
65 the top of the generated documentation inside a "h1" element.
70 Set the description used in the generated HTML documentation. This description
71 will appear as a paragraph, below the server name, in the documentation.
81 HTML documentation. This allows a server to provide its own web-based
[all …]
|
| D | pydoc.rst | 13 single: documentation; generation
14 single: documentation; online
21 The :mod:`pydoc` module automatically generates documentation from Python
22 modules. The documentation can be presented as pages of text on the console,
25 For modules, classes, functions and methods, the displayed documentation is
33 interactive interpreter, which uses :mod:`pydoc` to generate its documentation
34 as text on the console. The same text documentation can also be viewed from
40 at a shell prompt will display documentation on the :mod:`sys` module, in a
46 Unix), and refers to an existing Python source file, then documentation is
51 In order to find objects and their documentation, :mod:`pydoc` imports the
[all …]
|
| /external/libxml2/result/schemas/ |
| D | annot-err_0_0.err | 2 …3.org/2001/XMLSchema}annotation': The content is not valid. Expected is (appinfo | documentation)*.
5 …/annot-err_0.xsd:14: element documentation: Schemas parser error : Element '{http://www.w3.org/200…
6 …/annot-err_0.xsd:14: element documentation: Schemas parser error : Element '{http://www.w3.org/200…
7 …/annot-err_0.xsd:14: element documentation: Schemas parser error : Element '{http://www.w3.org/200…
|
| /external/netperf/ |
| D | COPYING | 6 The enclosed software and documentation includes copyrighted works
9 modify the software and documentation, and to (ii) distribute the
10 software and documentation, including modifications, for
13 1. The enclosed software and documentation is made available at no
18 software or documentation. All hard copies, and copies in
20 documentation (including modifications) must contain at least
23 3. The enclosed software and documentation has not been subjected
26 offer a version of the software and documentation as a product.
|
| D | MODULE_LICENSE_HP | 6 The enclosed software and documentation includes copyrighted works
9 modify the software and documentation, and to (ii) distribute the
10 software and documentation, including modifications, for
13 1. The enclosed software and documentation is made available at no
18 software or documentation. All hard copies, and copies in
20 documentation (including modifications) must contain at least
23 3. The enclosed software and documentation has not been subjected
26 offer a version of the software and documentation as a product.
|
| D | NOTICE | 6 The enclosed software and documentation includes copyrighted works
9 modify the software and documentation, and to (ii) distribute the
10 software and documentation, including modifications, for
13 1. The enclosed software and documentation is made available at no
18 software or documentation. All hard copies, and copies in
20 documentation (including modifications) must contain at least
23 3. The enclosed software and documentation has not been subjected
26 offer a version of the software and documentation as a product.
|
| /external/llvm/docs/ |
| D | README.txt | 4 LLVM's documentation is written in reStructuredText, a lightweight
6 reStructuredText documentation should be quite readable in source form, it
7 is mostly meant to be processed by the Sphinx documentation generation
19 The mapping between reStructuredText files and generated documentation is
22 If you are interested in writing new documentation, you will want to read
23 `SphinxQuickstartTemplate.rst` which will get you writing documentation
30 Building the manpages is similar to building the HTML documentation. The
49 The reachability of external links in the documentation can be checked by
|
| /external/libnl/doc/ |
| D | configure.ac | 21 # Generating the documentation
24 AS_HELP_STRING([--disable-doc], [Do not generate documentation]),
35 AC_MSG_ERROR([*** doxygen package required to generate documentation])
41 AC_MSG_ERROR([*** graphviz package required to generate documentation])
51 AC_MSG_ERROR([*** asciidoc package required to generate documentation])
60 AC_MSG_ERROR([*** source-highlight required to generate documentation])
71 AC_MSG_ERROR([*** mscgen package required to generate documentation])
82 AC_MSG_ERROR([*** pygmentize package required to generate documentation])
|
| /external/python/cpython2/Doc/ |
| D | about.rst | 7 document processor specifically written for the Python documentation.
13 changes directly on the documentation pages.
15 Development of the documentation and its toolchain is an entirely volunteer
22 * Fred L. Drake, Jr., the creator of the original Python documentation toolset
35 library, and the Python documentation. See :source:`Misc/ACKS` in the Python
39 that Python has such wonderful documentation -- Thank You!
|
| /external/swiftshader/third_party/LLVM/docs/ |
| D | Makefile | 57 $(Echo) Installing HTML documentation
65 $(Echo) Packaging HTML documentation
72 $(Echo) Installing doxygen documentation
82 $(Echo) Building doxygen documentation
89 $(Echo) Packaging doxygen documentation
103 $(Echo) Installing ocamldoc documentation
111 $(Echo) Packaging ocamldoc documentation
118 $(Echo) Building ocamldoc documentation
|
| D | doxygen.cfg.in | 3 # This file describes the settings to be used by the documentation system
31 # This could be handy for archiving the generated documentation or
37 # base path where the generated documentation will be put.
53 # documentation generated by doxygen is written. Doxygen will use this
67 # the file and class documentation (similar to JavaDoc).
98 # inherited members of a class in the documentation of that class as if those
120 # the path mentioned in the documentation of a class, which tells
159 # member inherits the documentation from any documented member that it
165 # a new page for each member. If set to NO, the documentation of a member will
176 # as commands in the documentation. An alias has the form "name=value".
[all …]
|
| /external/flatbuffers/include/flatbuffers/ |
| D | reflection_generated.h | 321 const flatbuffers::Vector<flatbuffers::Offset<flatbuffers::String>> *documentation() const { in documentation() function
338 verifier.Verify(documentation()) && in Verify()
339 verifier.VerifyVectorOfStrings(documentation()) && in Verify()
362 …flatbuffers::Offset<flatbuffers::Vector<flatbuffers::Offset<flatbuffers::String>>> documentation) { in add_documentation()
363 fbb_.AddOffset(Enum::VT_DOCUMENTATION, documentation); in add_documentation()
387 …buffers::Offset<flatbuffers::Vector<flatbuffers::Offset<flatbuffers::String>>> documentation = 0) {
389 builder_.add_documentation(documentation);
405 const std::vector<flatbuffers::Offset<flatbuffers::String>> *documentation = nullptr) {
413 … documentation ? _fbb.CreateVector<flatbuffers::Offset<flatbuffers::String>>(*documentation) : 0);
466 const flatbuffers::Vector<flatbuffers::Offset<flatbuffers::String>> *documentation() const { in documentation() function
[all …]
|
| /external/libexif/m4m/ |
| D | gp-documentation.m4 | 2 dnl check where to install documentation
4 dnl determines documentation "root directory", i.e. the directory
5 dnl where all documentation will be placed in
11 AS_HELP_STRING([--disable-docs], [whether to create any documentation])], [dnl
33 # check for the main ("root") documentation directory
54 # check whether to include package version into documentation path
82 # gtk-doc: We use gtk-doc for building our documentation. However, we
90 [Use gtk-doc to build documentation [default=no]])],[
109 # Give the user the possibility to install html documentation in a
|
| /external/libxml2/test/schemas/ |
| D | 570702_0.xsd | 8 <xs:documentation>Destination Number Length</xs:documentation>
19 <xs:documentation>destroy flag</xs:documentation>
|
| /external/curl/docs/ |
| D | README.md | 5 You'll find a mix of various documentation in this directory and
9 If you rather see the rendered version of the documentation, check out the
10 curl web site's [documentation section](https://curl.haxx.se/docs/) for
12 libcurl related documentation.
|
| /external/libogg/ |
| D | CHANGES | 14 * Updates to API documentation
21 * documentation fixes and cleanup
34 * new multiplexed Ogg stream documentation
41 * RFC 3533 documentation of the format by Silvia Pfeiffer at CSIRO
42 * RFC 3534 documentation of the application/ogg mime-type by Linus Walleij
|
| /external/eigen/doc/ |
| D | Overview.dox | 5 This is the API documentation for Eigen3. You can <a href="eigen-doc.tgz">download</a> it as a tgz …
17 The \b main \b documentation is organized into \em chapters covering different domains of features.
18 …hensive way, and \em reference pages that gives you access to the API documentation through the re…
22 Under the \subpage UserManual_Generalities section, you will find documentation on more general top…
24 Finally, do not miss the search engine, useful to quickly get to the documentation of a given class…
26 …more? Checkout the <a href="unsupported/index.html">\em unsupported \em modules </a> documentation.
|
| /external/ppp/pppd/plugins/radius/ |
| D | COPYRIGHT | 9 documentation, the name of Roaring Penguin Software Inc. not be used
12 documentation that copying and distribution is by permission of
24 permission notice appear on all copies and supporting documentation, the
27 given in supporting documentation that copying and distribution is by
40 and permission notice appear on all copies and supporting documentation,
43 prior permission, and notice be given in supporting documentation that
54 documentation for any purpose and without fee is hereby granted, provided
58 notice appear in supporting documentation.
89 documentation and/or software.
|
| /external/pcre/dist2/ |
| D | PrepareRelease | 4 # processing of the documentation, detrails files, and creates pcre2.h.generic
8 # is "doc", it stops after preparing the documentation. There are no other
25 # when the HTML documentation is built. It works like this so that
31 # documentation, because some people just go to the HTML without
35 # First, sort out the documentation. Remove pcre2demo.3 first because it won't
40 echo Processing documentation
49 # Make Text form of the documentation. It needs some mangling to make it
126 # Make HTML form of the documentation.
128 echo "Making HTML documentation"
160 # End of documentation processing; stop if only documentation required.
|
| /external/syslinux/core/lwip/doc/ |
| D | FILES | 3 rawapi.txt - The documentation for the core API of lwIP.
5 snmp_agent.txt - The documentation for the lwIP SNMP agent.
6 sys_arch.txt - The documentation for a system abstraction layer of lwIP.
|
| /external/antlr/antlr-3.4/runtime/C/doxygen/ |
| D | runtime.dox | 3 /// If you are familiar with Doxygen generated documentation, then the layout of the files, typedefs
22 …When navigating the source code, find the typedef you want to consult and inspect the documentation
23 /// for its function pointers, then look at the documentation for the default methods that implement
31 /// From here, the documentation should be obvious. If it is not, then you could try reading
34 /// C runtime documentation.
|
| /external/xmlrpcpp/src/ |
| D | Doxyfile | 3 # This file describes the settings to be used by the documentation system
23 # This could be handy for archiving the generated documentation or
29 # base path where the generated documentation will be put.
36 # documentation generated by doxygen is written. Doxygen will use this
47 # documentation are documented, even if no documentation was available.
54 # will be included in the documentation.
59 # will be included in the documentation.
64 # defined locally in source files will be included in the documentation.
72 # various overviews, but no documentation section is generated.
87 # documentation.
[all …]
|
| /external/mesa3d/doxygen/ |
| D | common.doxy | 3 # This file describes the settings to be used by the documentation system
23 # This could be handy for archiving the generated documentation or
29 # base path where the generated documentation will be put.
45 # documentation generated by doxygen is written. Doxygen will use this
58 # the file and class documentation (similar to JavaDoc).
88 # members of a class in the documentation of that class as if those members were
110 # the path mentioned in the documentation of a class, which tells
141 # member inherits the documentation from any documented member that it
146 # If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
147 # tag is set to YES, then doxygen will reuse the documentation of the first
[all …]
|
| /external/syslinux/gpxe/src/ |
| D | doxygen.cfg | 3 # This file describes the settings to be used by the documentation system
31 # This could be handy for archiving the generated documentation or
37 # base path where the generated documentation will be put.
53 # documentation generated by doxygen is written. Doxygen will use this
67 # the file and class documentation (similar to JavaDoc).
98 # inherited members of a class in the documentation of that class as if those
120 # the path mentioned in the documentation of a class, which tells
159 # member inherits the documentation from any documented member that it
165 # a new page for each member. If set to NO, the documentation of a member will
176 # as commands in the documentation. An alias has the form "name=value".
[all …]
|
| /external/antlr/antlr-3.4/runtime/C/ |
| D | doxyfile | 3 # This file describes the settings to be used by the documentation system
31 # This could be handy for archiving the generated documentation or
37 # base path where the generated documentation will be put.
53 # documentation generated by doxygen is written. Doxygen will use this
67 # the file and class documentation (similar to JavaDoc).
108 # inherited members of a class in the documentation of that class as if those
130 # the path mentioned in the documentation of a class, which tells
169 # member inherits the documentation from any documented member that it
175 # a new page for each member. If set to NO, the documentation of a member will
186 # as commands in the documentation. An alias has the form "name=value".
[all …]
|