| /external/chromium_org/chrome/browser/resources/sync_internals/ |
| events.html | 4 <th>Submodule</th>
14 <td jscontent="submodule" class="attrib-column"></td>
|
| sync_log.js | 89 * @param {string} submodule The sync submodule for the event.
93 log_: function(submodule, event, details) {
95 submodule: submodule,
|
| /external/clang/test/Modules/ |
| missing-submodule.m | 3 #include <Module/NotInModule.h> // expected-warning{{missing submodule 'Module.NotInModule'}}
|
| unnecessary-module-map-parsing.c | 6 // CHECK: error: expected umbrella, header, submodule, or module export
|
| submodules.cpp | 14 @import std.typetraits; // expected-error{{no submodule named 'typetraits' in module 'std'; did you mean 'type_traits'?}}
19 @import std.vector.compare; // expected-error{{no submodule named 'compare' in module 'std.vector'}}
|
| wildcard-submodule-exports.cpp | 2 // RUN: %clang_cc1 -x objective-c++ -fmodules-cache-path=%t -fmodules -I %S/Inputs/wildcard-submodule-exports %s -verify
|
| submodules-preprocess.cpp | 19 @import std.typetraits; // expected-error{{no submodule named 'typetraits' in module 'std'; did you mean 'type_traits'?}}
33 @import std.vector.compare; // expected-error{{no submodule named 'compare' in module 'std.vector'}}
|
| auto-module-import.m | 35 // Test umbrella-less submodule includes
39 // Test umbrella-less submodule includes
80 // expected-warning{{missing submodule 'Module.NotInModule'}}
|
| cxx-decls.cpp | 14 // ever been explicitly declared in an unimported submodule.
|
| /external/clang/test/Modules/Inputs/submodules/ |
| import-self-b.h | 1 // FIXME: This import has no effect, because the submodule isn't built yet, and
|
| /external/chromium_org/build/git-hooks/ |
| pre-commit | 32 Submodule commits are not allowed. Please run:
42 If you're really and truly trying to roll the version of a submodule, you should
55 To make changes to submodule names/paths, edit DEPS.
|
| /external/clang/test/VFS/ |
| module-import.m | 12 // Import a submodule that is defined in actual_module2.map, which is only
16 // CHECK-VFS2: error: no submodule
|
| /external/robolectric/ |
| update-downloads.rb | 7 raise "Robolectric pages submodule isn't present. Run git submodule update --init"
|
| /prebuilts/python/darwin-x86/2.7.5/lib/python2.7/test/ |
| test_pkg.py | 33 # __init__ importing submodule
36 # submodule importing other submodule
37 # submodule importing global module
38 # submodule import submodule via global name
39 # from package import submodule
|
| pydocfodder.py | 215 submodule = types.ModuleType(__name__ + '.submodule', variable
216 """A submodule, which should appear in its parent's summary""")
|
| /prebuilts/python/linux-x86/2.7.5/lib/python2.7/test/ |
| test_pkg.py | 33 # __init__ importing submodule
36 # submodule importing other submodule
37 # submodule importing global module
38 # submodule import submodule via global name
39 # from package import submodule
|
| pydocfodder.py | 215 submodule = types.ModuleType(__name__ + '.submodule', variable
216 """A submodule, which should appear in its parent's summary""")
|
| /external/clang/include/clang/Basic/ |
| Module.h | 46 /// \brief Describes a module or submodule.
77 /// \brief A mapping from the submodule name to the index into the
78 /// \c SubModules vector at which that submodule resides.
141 /// \brief Whether this is an explicit submodule.
153 /// \brief Whether this is an inferred submodule (module * { ... }).
195 /// \brief The location of the inferred submodule.
285 /// \brief Construct a new module or submodule.
313 /// \brief Determine whether this module is a submodule.
316 /// \brief Determine whether this module is a submodule of the given other
321 /// either because it is a framework module or because it is a submodule
[all...] |
| DiagnosticFrontendKinds.td | 158 def err_no_submodule : Error<"no submodule named %0 in module '%1'">;
160 "no submodule named %0 in module '%1'; did you mean '%2'?">;
161 def warn_missing_submodule : Warning<"missing submodule '%0'">,
|
| /external/clang/docs/ |
| Modules.rst | 117 The @import declaration above imports the entire contents of the ``std`` module (which would contain, e.g., the entire C or C++ standard library) and make its API available within the current translation unit. To import only part of a module, one may use dot syntax to specific a particular submodule, e.g.,
145 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.
207 Modules are modeled as if each submodule were a separate translation unit, and a module import makes names from the other translation unit visible. Each submodule starts with a new preprocessor state and an empty translation unit.
211 This behavior is currently only approximated when building a module. Entities within a submodule that has already been built are visible when building later submodules in that module. This can lead to fragile modules that depend on the build order used for the submodules of the module, and should not be relied upon.
225 * Such entities are *visible* if they are from the current submodule or translation unit, or if they were exported from a submodule that has been imported.
282 Here, the top-level module ``std`` encompasses the whole C standard library. It has a number of submodules containing different parts of the standard library: ``complex`` for complex numbers, ``ctype`` for character types, etc. Each submodule lists one of more headers that provide the contents for that submodule. Finally, the ``export *`` command specifies that anything included by that submodule will be automatically re-exported.
[all...] |
| /external/chromium_org/third_party/polymer_legacy/platform/ |
| CONTRIBUTING.md | 32 git submodule init
33 git submodule update
|
| /external/chromium_org/chrome/browser/sync_file_system/ |
| sync_status_code.h | 23 // submodule error code (yet).
|
| /external/clang/include/clang/Lex/ |
| ModuleLoader.h | 29 /// module or submodule, e.g., std.vector.
45 /// actually a submodule that we expected to see (based on implying the
46 /// submodule from header structure), but didn't materialize in the actual
|
| /external/chromium_org/third_party/cython/src/Cython/Includes/cpython/ |
| module.pxd | 14 # submodule of a package), the fromlist argument is set to the
18 # when name in fact specifies a subpackage instead of a submodule:
33 # case). Like for __import__(), the return value when a submodule
|
| /external/chromium_org/native_client_sdk/src/gonacl_appengine/src/smoothlife/ |
| build.sh | 71 LogExecute git submodule update --init
|
