Documentation (full) in projects: third_party

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched full:documentation (Results 1 – 25 of 14313) sorted by relevance

12 3 4 5 6 7 8 9 10 >>...573

/third_party/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 …]`
/third_party/typescript/tests/baselines/reference/
D	jsdocDisallowedInTypescript.errors.txt	1 …wedInTypescript.ts(2,15): error TS8020: JSDoc types can only be used inside documentation comments. 2 …wedInTypescript.ts(4,15): error TS8020: JSDoc types can only be used inside documentation comments. 3 …wedInTypescript.ts(4,32): error TS8020: JSDoc types can only be used inside documentation comments. 4 …wedInTypescript.ts(7,20): error TS8020: JSDoc types can only be used inside documentation comments. 5 …edInTypescript.ts(10,18): error TS8020: JSDoc types can only be used inside documentation comments. 7 …edInTypescript.ts(13,14): error TS8020: JSDoc types can only be used inside documentation comments. 8 …edInTypescript.ts(14,11): error TS8020: JSDoc types can only be used inside documentation comments. 9 …wedInTypescript.ts(15,8): error TS8020: JSDoc types can only be used inside documentation comments. 10 …edInTypescript.ts(16,11): error TS8020: JSDoc types can only be used inside documentation comments. 11 …edInTypescript.ts(17,17): error TS8020: JSDoc types can only be used inside documentation comments. [all …]
D	quickInfoDisplayPartsEnum1.baseline	`28 "documentation": [] 89 "documentation": [] 150 "documentation": [] 211 "documentation": [] 252 "documentation": [] 281 "documentation": [] 322 "documentation": [] 351 "documentation": [] 412 "documentation": [] 453 "documentation": [] [all …]`
D	quickInfoDisplayPartsExternalModules.baseline	`28 "documentation": [] 69 "documentation": [] 118 "documentation": [] 167 "documentation": [] 196 "documentation": [] 245 "documentation": [] 274 "documentation": [] 303 "documentation": [] 340 "documentation": [] 381 "documentation": [] [all …]`
D	quickInfoDisplayPartsModules.baseline	`28 "documentation": [] 69 "documentation": [] 118 "documentation": [] 167 "documentation": [] 196 "documentation": [] 245 "documentation": [] 274 "documentation": [] 303 "documentation": [] 340 "documentation": [] 381 "documentation": [] [all …]`
D	quickInfoDisplayPartsEnum3.baseline	`28 "documentation": [] 93 "documentation": [] 158 "documentation": [] 223 "documentation": [] 264 "documentation": [] 293 "documentation": [] 334 "documentation": [] 363 "documentation": [] 428 "documentation": [] 469 "documentation": [] [all …]`
D	quickInfoDisplayPartsEnum2.baseline	`28 "documentation": [] 93 "documentation": [] 158 "documentation": [] 223 "documentation": [] 264 "documentation": [] 293 "documentation": [] 334 "documentation": [] 363 "documentation": [] 428 "documentation": [] 469 "documentation": [] [all …]`
/third_party/boost/libs/beast/test/extras/include/boost/beast/
D	doc_debug.hpp	`15 /// doc type (documentation debug helper) 18 /// doc enum (documentation debug helper) 21 /// One (documentation debug helper) 24 /// Two (documentation debug helper) 28 /// doc enum class (documentation debug helper) 31 /// one (documentation debug helper) 34 /// two (documentation debug helper) 38 /// doc func (documentation debug helper) 41 /// doc class (documentation debug helper) 44 /// doc class member func (documentation debug helper) [all …]`
/third_party/mesa3d/src/freedreno/registers/
D	rules-ng.xsd	`8 <documentation> 15 </documentation> 16 <documentation>Version 0.1</documentation> 44 <!-- Documentation elements --> 62 <documentation> 64 </documentation> 75 <documentation>nickType</documentation> 84 <documentation>databaseType</documentation> 94 <documentation>importType</documentation> 101 <documentation>copyrightType</documentation> [all …]`
/third_party/gstreamer/gstreamer/docs/
D	README	1 GStreamer documentation notes 6 Our documentation uses hotdoc, you should usually refer to the 7 [hotdoc documentation](http://hotdoc.github.io/). 9 GStreamer has two sets of documentation but both are controlled and aggregated in 17 To build the full documentation you should make sure to have `hotdoc` installed and 24 And building the documentation: 27 ninja -C build/ subprojects/gst-docs/GStreamer-doc`, this will result in two documentation sets: 37 Hotdoc build targets are generated for each documentation 'components' (ie. hotdoc 38 subprojects). This includes libraries documentation and one target per GStreamer plugin. 40 One can build a specific documentation target by explicitly building the target, [all …]
/third_party/wayland_standard/
D	configure.ac	86 AC_ARG_ENABLE([documentation], optenable 87 [AC_HELP_STRING([--disable-documentation], 88 [Disable building the documentation])], 138 …C_MSG_ERROR([Documentation build requested but doxygen not found. Install doxygen or disable the d… 145 …n 1.6+ required for documentation build. Install required doxygen version or disable the documenta… 152 …AC_MSG_ERROR([Documentation build requested but xmlto not found. Install xmlto or disable the docu… 157 …G_ERROR([Documentation build requested but graphviz's dot not found. Install graphviz or disable t… 163 … 2.26+ required for documentation build. Install required graphviz version or disable the document… 174 …Documentation build requested but docbook-xsl stylesheets are not found. Install the docbook-xsl p…
/third_party/skia/third_party/externals/dng_sdk/
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	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	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 …]
/third_party/python/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 …]
/third_party/boost/more/writingdoc/
D	introduction.html	9 <title>Writing Documentation for Boost - Introduction</title> 22 <h1 align="center">Writing Documentation for Boost</h1> 31 documentation. If you are submitting a library that already has written 32 documentation in HTML format, there is no reason to change it to follow any 33 of the guidelines presented here. However, if you have documentation that's 35 starting on a library from scratch or have a library with no documentation 36 then these guidelines can make writing the documentation much easier.</p> 38 <p>The section on <a href="structure.html">Documentation Structure</a> 39 describes how to go about structuring the documentation's content. This 40 section may be helpful even for libraries that already have documentation. [all …]
D	design.html	9 <title>Writing Documentation for Boost - HTML Design</title> 22 <h1 align="center">Writing Documentation for Boost</h1> 34 Documentation</a></dt> 66 <dt><a href="#content">Documentation Content</a></dt> 126 <p>Boost places no requirements on the design of HTML documentation for 127 library submitters. If you are submitting a library for which documentation 130 yet written the documentation, or if you expect to have to translate 131 documentation written in a format not easily convertible to HTML then this 133 documentation in HTML.</p> 135 <p>In several places this document assumes you're writing the documentation [all …]
/third_party/typescript/tests/cases/fourslash/
D	commentsExternalModules.ts	40 { name: "b", text: "var b: number", documentation: "b's comment" }, 41 { name: "foo", text: "function foo(): number", documentation: "foo's comment" }, 50 includes: { name: "m1", text: "namespace m1", documentation: "Namespace comment" }, 56 { name: "b", text: "var m1.b: number", documentation: "b's comment" }, 57 …{ name: "fooExport", text: "function m1.fooExport(): number", documentation: "exported function" }, 58 { name: "m2", text: "namespace m1.m2", documentation: "m2 comments" }, 70 { name: "c", text: "constructor m1.m2.c(): m1.m2.c", documentation: "class comment;" }, 71 { name: "i", text: "var m1.m2.i: m1.m2.c", documentation: "i" }, 81 …, text: 'import extMod = require("./commentsExternalModules_file0")', documentation: "This is on i… 85 includes: { name: "m1", text: "namespace extMod.m1", documentation: "Namespace comment" }, [all …]
D	jsDocInheritDoc.ts	5 //// * Foo constructor documentation 9 //// * Foo#method1 documentation 13 //// * Foo#method2 documentation 17 //// * Foo#property1 documentation 22 //// /** Baz#property1 documentation / 25 //// Baz#property2 documentation 54 verify.quickInfoAt("2", "(method) Bar.method2(): void", "Foo#method2 documentation"); // use inheri… 56 verify.quickInfoAt("4", "(property) Bar.property1: string", "Foo#property1 documentation"); // use … 57 verify.quickInfoAt("5", "(property) Bar.property2: object", "Baz#property2 documentation\nBar#prope…
/third_party/boost/libs/test/doc/
D	README.md	1 This folder contains the documentation for the Boost.Test library. 2 …contribution or submission to the library should be accompanied by the corresponding documentation. 4 The format of the documentation uses [Quickbook](http://www.boost.org/tools/quickbook/index.html). 6 How to build the documentation 9 In order to generate the documentation, the following is needed: 17 Part of the documentation needs [Doxygen](http://www.doxygen.org). `doxygen` should be accessible f… 43 Build the documentation 46 Running the following commands will construct the documentation with `b2` and 64 - Documentation is part of the "definition of done". A feature does not exist until it is implement… 65 - It is highly recommended that each of your pull request comes with an updated documentation. Not …
/third_party/boost/tools/quickbook/doc/boost-doc-tools/
D	parameters.qbk	23 split the documentation into a file for each section: 33 documentation, but there are far more than can be listed here. 37 DocBook XSL documentation] for a full list. This also isn't a complete list 45 customise the documentation build in several places, it should all be 78 DocBook Reference documentation] 101 DocBook Reference Documentation] 108 This is mainly used in the Boost.Math documentation but could be useful in 114 When linking to other documentation Boost, differnet links need to be 115 generated for different documentation styles. HTML documentation needs to use 118 the documentation is viewed. [all …]
/third_party/ltp/tools/sparse/sparse-src/Documentation/
D	doc-guide.rst	1 Documentation guide 8 The documentation for Sparse is written in plain text augmented with 11 of the documentation. 12 Sparse uses `Sphinx`_ to format this documentation in several formats, 15 All documentation related files are in the ``Documentation/`` directory. 17 the documentation in HTML or manpage format. The generated files can then 20 The root of the documentation is the file ``index.rst`` which mainly 21 lists the names of the files with real documentation. 120 .. c:autodoc:: Documentation/sphinx/cdoc.py 155 .. c:autodoc:: Documentation/sphinx/ir.py
/third_party/boost/libs/utility/meta/
D	libraries.json	`9 "documentation": "utility.htm", string 25 "documentation": "call_traits.htm", string 37 "documentation": "compressed_pair.htm", string 50 "documentation": "identity_type/", string 65 "documentation": "in_place_factories.html", string 78 "documentation": "operators.htm", string 92 "documentation": "utility.htm#result_of", string 105 "documentation": "doc/html/string_ref.html", string 121 "documentation": "value_init.htm", string`
/third_party/node/doc/api/
D	deprecations.md	14 * Documentation-only 18 A Documentation-only deprecation is one that is expressed only within the 20 Some Documentation-only deprecations trigger a runtime warning when launched 23 deprecations below. Documentation-only deprecations that support that flag 116 description: Documentation-only deprecation. 134 description: Documentation-only deprecation. 177 description: Documentation-only deprecation. 200 description: Documentation-only deprecation. 220 description: Documentation-only deprecation. 223 Type: Documentation-only [all …]

12 3 4 5 6 7 8 9 10 >>...573