| /external/libxml2/test/schemas/ |
| D | nvdcve_0.xsd | 8 <xs:documentation>This schema defines the structure of the National
20 how to interpret this data. </xs:documentation>
24 …<xs:documentation>The root element of the NVD CVE feed. Multiple "entry" child elements describe s…
32 <xs:documentation>The schema version number supported by the feed.</xs:documentation>
37 <xs:documentation>The date the feed was generated.</xs:documentation>
45 <xs:documentation>A CVE entry.</xs:documentation>
54 <xs:documentation> Documents one CVE entry. The child elements should always
56 entry elements from the CVE XML feeds.</xs:documentation>
61 <xs:documentation>Description wrapper tag, parent to any
65 description source (i.e. CVE, NVD, ...). </xs:documentation>
[all …]
|
| D | changelog093_1.xsd | 12 <xsd:documentation>
16 </xsd:documentation>
64 <xsd:documentation>
68 </xsd:documentation>
79 <xsd:documentation>
82 </xsd:documentation>
93 <xsd:documentation>
97 </xsd:documentation>
106 <xsd:documentation>
110 </xsd:documentation>
[all …]
|
| /external/clang/include/clang/Basic/ |
| D | Attr.td | 10 // The documentation is organized by category. Attributes can have category-
11 // specific documentation that is collated within the larger document.
21 // documentation. Ideally, this category should be used for internal-only
27 // documentation. Otherwise, the documentation will specify the attribute has
32 // Specifies the documentation to be associated with the given category.
33 class Documentation {
52 def Undocumented : Documentation {
306 // Any documentation that should be associated with the attribute. Since an
308 // Documentation entry may be listed.
309 list<Documentation> Documentation;
[all …]
|
| D | DiagnosticCommentKinds.td | 11 let CategoryName = "Documentation Issue" in {
18 InGroup<Documentation>, DefaultIgnore;
22 InGroup<Documentation>, DefaultIgnore;
52 InGroup<Documentation>, DefaultIgnore;
56 InGroup<Documentation>, DefaultIgnore;
69 InGroup<Documentation>, DefaultIgnore;
78 InGroup<Documentation>, DefaultIgnore;
85 InGroup<Documentation>, DefaultIgnore;
91 InGroup<Documentation>, DefaultIgnore;
97 InGroup<Documentation>, DefaultIgnore;
[all …]
|
| D | AttrDocs.td | 1 //==--- AttrDocs.td - Attribute documentation ----------------------------===//
30 def SectionDocs : Documentation {
39 def InitSegDocs : Documentation {
49 documentation on MSDN for more information.
55 def TLSModelDocs : Documentation {
70 def ThreadDocs : Documentation {
75 compatibility. See the documentation for `__declspec(thread)`_ on MSDN.
87 def CarriesDependencyDocs : Documentation {
104 def C11NoReturnDocs : Documentation {
113 def CXX11NoReturnDocs : Documentation {
[all …]
|
| /external/google-styleguide/docguide/ |
| D | best_practices.md | 1 # Documentation Best Practices
8 1. [Minimum viable documentation](#minimum-viable-documentation)
10 1. [Delete dead documentation](#delete-dead-documentation)
11 1. [Documentation is the story of your code](#documentation-is-the-story-of-your-code)
13 ## Minimum viable documentation
16 assembly of "documentation" in various states of disrepair.
32 **Change your documentation in the same CL as the code change**. This keeps your
39 ## Delete dead documentation
59 Your documentation should be as good as possible within a reasonable time frame.
60 The standards for an documentation review are different from the
[all …]
|
| /external/python/cpython2/Doc/library/ |
| D | pydoc.rst | 1 :mod:`pydoc` --- Documentation generator and online help system
5 :synopsis: Documentation generator and online help system.
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
[all …]
|
| 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 …]
|
| /external/python/cpython2/Lib/ |
| D | DocXMLRPCServer.py | 4 serve pydoc-style documentation in response to HTTP
5 GET requests. This documentation is dynamically generated
69 """Produce HTML documentation for a function or method object."""
110 """Produce HTML documentation for an XML-RPC server."""
135 """Generates documentation for an XML-RPC server.
142 # setup variables used for HTML documentation
143 self.server_name = 'XML-RPC Server Documentation'
147 self.server_title = 'XML-RPC Server Documentation'
150 """Set the HTML title of the generated server documentation"""
155 """Set the name of the generated HTML server documentation"""
[all …]
|
| /external/python/google-api-python-client/samples/ |
| D | README.md | 7 Documentation for the Ad Exchange Buyer API in
8 [PyDoc](https://google-api-client-libraries.appspot.com/documentation/adexchangebuyer/v1.3/python/l…
22 Documentation for the AdSense Management API in
23 [PyDoc](https://google-api-client-libraries.appspot.com/documentation/adsense/v1.3/python/latest/).
36 Documentation for the Google Analytics API in
37 [PyDoc](https://google-api-client-libraries.appspot.com/documentation/analytics/v3/python/latest/).
51 Documentation for the Enterprise Audit API in
52 [PyDoc](https://google-api-client-libraries.appspot.com/documentation/audit/v1/python/latest/).
65 Documentation for the Blogger API in
66 [PyDoc](https://google-api-client-libraries.appspot.com/documentation/blogger/v3/python/latest/).
[all …]
|
| /external/python/cpython3/Doc/library/ |
| D | pydoc.rst | 1 :mod:`pydoc` --- Documentation generator and online help system
5 :synopsis: Documentation generator and online help system.
13 single: documentation; generation
14 single: documentation; online
19 The :mod:`pydoc` module automatically generates documentation from Python
20 modules. The documentation can be presented as pages of text on the console,
23 For modules, classes, functions and methods, the displayed documentation is
31 interactive interpreter, which uses :mod:`pydoc` to generate its documentation
32 as text on the console. The same text documentation can also be viewed from
38 at a shell prompt will display documentation on the :mod:`sys` module, in a
[all …]
|
| /external/dng_sdk/ |
| D | LICENSE | 6 Adobe Systems Incorporated provides the Software and Documentation for use under
8 modification or distribution of the Software or Documentation, or any
13 accompanying this Agreement. "Documentation" means the documents, specifications
24 copies of the Documentation for your development purposes and to publicly
26 Documentation.
30 Documentation and you will include such notices in any copies of the Software
34 Documentation in any manner not permitted by this Agreement. No title to the
35 intellectual property in the Software or Documentation is transferred to you
37 or the Documentation except as expressly set forth in this Agreement. All rights
41 ADOBE PROVIDES THE SOFTWARE AND DOCUMENTATION ONLY ON AN "AS IS" BASIS WITHOUT
[all …]
|
| D | LICENSE.source_code | 3 Adobe Systems Incorporated provides the Software and Documentation for use under
5 modification or distribution of the Software or Documentation, or any
10 accompanying this Agreement. "Documentation" means the documents, specifications
21 copies of the Documentation for your development purposes and to publicly
23 Documentation.
27 Documentation and you will include such notices in any copies of the Software
31 Documentation in any manner not permitted by this Agreement. No title to the
32 intellectual property in the Software or Documentation is transferred to you
34 or the Documentation except as expressly set forth in this Agreement. All rights
38 ADOBE PROVIDES THE SOFTWARE AND DOCUMENTATION ONLY ON AN "AS IS" BASIS WITHOUT
[all …]
|
| D | NOTICE | 13 Adobe Systems Incorporated provides the Software and Documentation for use under
15 modification or distribution of the Software or Documentation, or any
20 accompanying this Agreement. "Documentation" means the documents, specifications
31 copies of the Documentation for your development purposes and to publicly
33 Documentation.
37 Documentation and you will include such notices in any copies of the Software
41 Documentation in any manner not permitted by this Agreement. No title to the
42 intellectual property in the Software or Documentation is transferred to you
44 or the Documentation except as expressly set forth in this Agreement. All rights
48 ADOBE PROVIDES THE SOFTWARE AND DOCUMENTATION ONLY ON AN "AS IS" BASIS WITHOUT
[all …]
|
| /external/wayland/ |
| D | configure.ac | 78 AC_ARG_ENABLE([documentation], optenable
79 [AC_HELP_STRING([--disable-documentation],
80 [Disable building the documentation])],
153 …C_MSG_ERROR([Documentation build requested but doxygen not found. Install doxygen or disable the d…
160 …n 1.6+ required for documentation build. Install required doxygen version or disable the documenta…
167 …AC_MSG_ERROR([Documentation build requested but xmlto not found. Install xmlto or disable the docu…
172 …G_ERROR([Documentation build requested but graphviz's dot not found. Install graphviz or disable t…
178 … 2.26+ required for documentation build. Install required graphviz version or disable the document…
|
| /external/flatbuffers/include/flatbuffers/ |
| D | reflection_generated.h | 259 const flatbuffers::Vector<flatbuffers::Offset<flatbuffers::String>> *documentation() const { in documentation() function
272 verifier.VerifyVector(documentation()) && in Verify()
273 verifier.VerifyVectorOfStrings(documentation()) && in Verify()
293 …flatbuffers::Offset<flatbuffers::Vector<flatbuffers::Offset<flatbuffers::String>>> documentation) { in add_documentation()
294 fbb_.AddOffset(EnumVal::VT_DOCUMENTATION, documentation); in add_documentation()
315 …buffers::Offset<flatbuffers::Vector<flatbuffers::Offset<flatbuffers::String>>> documentation = 0) {
318 builder_.add_documentation(documentation);
331 const std::vector<flatbuffers::Offset<flatbuffers::String>> *documentation = nullptr) {
333 …auto documentation__ = documentation ? _fbb.CreateVector<flatbuffers::Offset<flatbuffers::String>>…
373 const flatbuffers::Vector<flatbuffers::Offset<flatbuffers::String>> *documentation() const { in documentation() function
[all …]
|
| /external/clang/test/Index/ |
| D | comment-cplus11-specific.cpp | 8 //! This documentation should be inherited.
11 // CHECK: (CXComment_Text Text=[ This documentation should be inherited.])))]
14 //! This is documentation for the typedef (which shows up).
16 // CHECK: (CXComment_Text Text=[ This is documentation for the typedef (which shows up).]))…
18 //! This is documentation for the alias (which shows up).
20 // CHECK: (CXComment_Text Text=[ This is documentation for the alias (which shows up).])))]
23 // CHECK: (CXComment_Text Text=[ This documentation should be inherited.])))]
26 // CHECK: (CXComment_Text Text=[ This documentation should be inherited.])))]
|
| /external/llvm/docs/ |
| D | README.txt | 1 LLVM Documentation
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/libxml2/test/relaxng/ |
| D | docbook_0.xml | 81 document under the terms of the <citetitle>GNU Free Documentation
85 of the <citetitle>GNU Free Documentation License</citetitle> from
94 GNOME documentation, and those trademarks are made aware to the members
95 of the GNOME Documentation Project, the names have been printed in caps
100 <title>The GNOME Handbook of Writing Software Documentation</title>
109 <!-- ####### Introduction | The GNOME Documentation Project ####### -->
112 <title>The GNOME Documentation Project</title>
117 The GNOME Documentation Project (GDP) aims to provide GNOME
119 documentation system. At the center of the GDP is the
121 presents a unified interface to GNOME-specific documentation
[all …]
|
| /external/parameter-framework/upstream/schemas/ |
| D | W3cXmlAttributes.xsd | 5 <xs:documentation>
51 </xs:documentation>
55 <xs:documentation>This schema defines attributes and an attribute group
75 element with any of those attributes</xs:documentation>
79 <xs:documentation>In keeping with the XML Schema WG's standard versioning
91 </xs:documentation>
96 <xs:documentation>Attempting to install the relevant ISO 2- and 3-letter
104 the empty string.</xs:documentation>
128 <xs:documentation>See http://www.w3.org/TR/xmlbase/ for
129 information about this attribute.</xs:documentation>
[all …]
|
| /external/swiftshader/third_party/llvm-7.0/llvm/docs/ |
| D | README.txt | 1 LLVM Documentation
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/easymock/src/org/easymock/ |
| D | EasyMock.java | 209 * documentation.
219 * Expects any byte argument. For details, see the EasyMock documentation.
229 * Expects any char argument. For details, see the EasyMock documentation.
239 * Expects any int argument. For details, see the EasyMock documentation.
249 * Expects any long argument. For details, see the EasyMock documentation.
259 * Expects any float argument. For details, see the EasyMock documentation.
269 * Expects any double argument. For details, see the EasyMock documentation.
279 * Expects any short argument. For details, see the EasyMock documentation.
289 * Expects any Object argument. For details, see the EasyMock documentation.
301 * the EasyMock documentation.
[all …]
|
| /external/swiftshader/third_party/LLVM/docs/ |
| 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/antlr/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 …]
|
| /external/libmtp/doc/ |
| D | Doxyfile.in | 3 # This file describes the settings to be used by the documentation system
23 # This could be handy for archiving the generated documentation or
30 # base path where the generated documentation will be put.
46 # documentation generated by doxygen is written. Doxygen will use this
59 # the file and class documentation (similar to JavaDoc).
89 # members of a class in the documentation of that class as if those members were
111 # the path mentioned in the documentation of a class, which tells
144 # documentation.
149 # member inherits the documentation from any documented member that it
154 # If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
[all …]
|