| /external/apache-xml/src/main/java/org/apache/xalan/templates/ |
| Constants.java | 242 ATTRNAME_OUTPUT_STANDALONE = "standalone",
|
| /external/autotest/scheduler/shard/ |
| shard_client.py | 33 The shard client can be run as standalone service. It periodically polls the
|
| /external/bison/ |
| TODO | 46 (standalone symbol).
|
| /external/clang/docs/ |
| Modules.rst | 80 However, this module import behaves quite differently from the corresponding ``#include <stdio.h>``: when the compiler sees the module import above, it loads a binary representation of the ``std.io`` module and makes its API available to the application directly. Preprocessor definitions that precede the import declaration have no impact on the API provided by ``std.io``, because the module itself was compiled as a separate, standalone module. Additionally, any linker flags required to use the ``std.io`` module will automatically be provided when the module is imported [#]_
85 * **Fragility**: Each module is parsed as a standalone entity, so it has a consistent preprocessor environment. This completely eliminates the need for ``__underscored`` names and similarly defensive tricks. Moreover, the current preprocessor definitions when an import declaration is encountered are ignored, so one software library can not affect how another software library is compiled, eliminating include-order dependencies.
87 * **Tool confusion**: Modules describe the API of software libraries, and tools can reason about and present a module as a representation of that API. Because modules can only be built standalone, tools can rely on the module definition to ensure that they get the complete API for the library. Moreover, modules can specify which languages they work with, so, e.g., one can not accidentally attempt to load a C++ module into a C program.
154 The crucial link between modules and headers is described by a *module map*, which describes how a collection of existing headers maps on to the (logical) structure of a module. For example, one could imagine a module ``std`` covering the C standard library. Each of the C standard library headers (``<stdio.h>``, ``<stdlib.h>``, ``<math.h>``, etc.) would contribute to the ``std`` module, by placing their respective APIs into the corresponding submodule (``std.io``, ``std.lib``, ``std.math``, etc.). Having a list of the headers that are part of the ``std`` module allows the compiler to build the ``std`` module as a standalone entity, and having the mapping from header names to (sub)modules allows the automatic translation of ``#include`` directives to module imports.
[all...] |
| /external/icu/icu4c/source/i18n/ |
| gregoimp.h | 336 * for example, calendar/dayNames/standalone/narrow
|
| /external/icu/icu4c/source/test/cintltst/ |
| cdattst.c | [all...] |
| /external/libcxxabi/ |
| CMakeLists.txt | 125 # static libc++abi. In the case of a standalone build, the tests will link the
|
| /external/libxml2/ |
| parserInternals.c | 442 * the literal two-character sequence "#xD#xA" or a standalone
582 * sequence "#xD#xA" or a standalone literal #xD, an XML processor
[all...] |
| /external/libxml2/python/tests/ |
| reader.py | 411 doc="""<?xml version="1.0" standalone="no"?>
|
| /external/libxml2/test/valid/dtds/ |
| xmlspec.dtd | 64 <!-- Entities for classes of standalone elements ................... -->
136 <!-- Entities for mixtures of standalone elements .................. -->
175 and %illus.class;, considered standalone elements. -->
477 <!-- Standalone elements ........................................... -->
[all...] |
| /external/llvm/docs/ |
| LLVMBuild.rst | 291 ``Tool`` components define standalone command line tools which should be
|
| /external/llvm/docs/tutorial/ |
| LangImpl1.rst | 79 takes to add debug information to standalone executables. This debug
|
| /external/llvm/lib/Target/ARM/MCTargetDesc/ |
| ARMBaseInfo.h | 10 // This file contains small standalone helper functions and enum definitions for
|
| /external/lzma/DOC/ |
| lzma-sdk.txt | 138 Alone7z - 7zr.exe: Standalone 7-Zip console program (reduced version)
|
| /external/lzma/Java/Tukaani/src/org/tukaani/xz/ |
| XZInputStream.java | 21 * Use this to decompress regular standalone .xz files. This reads from
|
| /external/mdnsresponder/mDNSPosix/ |
| ReadMe.txt | 84 o Standalone products for dedicated devices (printer, network camera, etc.)
|
| /external/owasp/sanitizer/tools/findbugs/src/xsl/ |
| default.xsl | 54 standalone="yes"
|
| plain.xsl | 28 standalone="yes"
|
| /external/pcre/dist/doc/html/ |
| pcrematching.html | 152 matched as if it were a standalone pattern at the current point, and the
|
| /external/pdfium/core/src/fxge/skia/ |
| fx_skia_device.cpp | 154 // But only for standalone segment. TESTDOC: bug #1434 - maze.pdf;
|
| /external/tinyxml/docs/ |
| functions.html | 106 : <a class="el" href="classTiXmlAttribute.html#a14">TiXmlAttribute</a>, <a class="el" href="classTiXmlNode.html#a4">TiXmlNode</a><li>Standalone()
|
| functions_func.html | 101 : <a class="el" href="classTiXmlAttribute.html#a14">TiXmlAttribute</a>, <a class="el" href="classTiXmlNode.html#a4">TiXmlNode</a><li>Standalone()
|
| /external/valgrind/coregrind/m_syswrap/ |
| priv_syswrap-generic.h | 233 Wrappers for sockets and ipc-ery. These are split into standalone
|
| /external/valgrind/coregrind/ |
| vgdb.c | 53 2. standalone to send monitor commands to a running valgrind-ified process
66 As a standalone utility, vgdb builds command packets to write to valgrind,
[all...] |
| /external/webrtc/webrtc/base/ |
| BUILD.gn | 469 # expected to be when building json outside of the standalone build.
|
