| /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""")
|
| /hardware/bsp/intel/peripheral/libmraa/cmake/modules/ |
| GetGitRevisionDescription.cmake | 56 # check if this is a submodule
58 file(READ ${GIT_DIR} submodule)
59 string(REGEX REPLACE "gitdir: (.*)\n$" "\\1" GIT_DIR_RELATIVE ${submodule})
|
| /hardware/bsp/intel/peripheral/libupm/cmake/modules/ |
| GetGitRevisionDescription.cmake | 56 # check if this is a submodule
58 file(READ ${GIT_DIR} submodule)
59 string(REGEX REPLACE "gitdir: (.*)\n$" "\\1" GIT_DIR_RELATIVE ${submodule})
|
| /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/clang/test/Modules/ |
| diagnostics.modulemap | 16 module submodule { use foo }
|
| libstdcxx-ambiguous-internal.cpp | 3 // RUN: %clang_cc1 -x c++ -std=c++11 -fmodules -emit-module -fmodule-name=std -fmodules-cache-path=%t %S/Inputs/libstdcxx-ambiguous-internal/module.modulemap -fmodules-local-submodule-visibility -DAMBIGUOUS 2>&1| FileCheck %s
|
| merge-class-definition-visibility.cpp | 5 // RUN: -fmodules-local-submodule-visibility
|
| auto-import-unavailable.cpp | 13 // MISSING-HEADER-DAG: auto-import-unavailable.cpp:[[@LINE+1]]:10: note: submodule of top-level module 'missing_header' implicitly imported here
42 // MISSING-REQUIREMENT: auto-import-unavailable.cpp:[[@LINE+1]]:10: note: submodule of top-level module 'missing_requirement' implicitly imported here
|
| using-decl.cpp | 4 // RUN: %clang_cc1 -x objective-c++ -std=c++11 -fmodules -fimplicit-module-maps -fmodules-cache-path=%t -I %S/Inputs %s -verify -DEARLY_IMPORT -fmodules-local-submodule-visibility
5 // RUN: %clang_cc1 -x objective-c++ -std=c++11 -fmodules -fimplicit-module-maps -fmodules-cache-path=%t -I %S/Inputs %s -verify -UEARLY_IMPORT -fmodules-local-submodule-visibility
|
| cxx-decls.cpp | 14 // ever been explicitly declared in an unimported submodule.
|
| submodules-merge-defs.cpp | 4 // RUN: %clang_cc1 -x c++ -std=c++11 -fmodules-cache-path=%t -fmodules -fimplicit-module-maps -I %S/Inputs/submodules-merge-defs %s -verify -fno-modules-error-recovery -fmodules-local-submodule-visibility -DTEXTUAL
5 // RUN: %clang_cc1 -x c++ -std=c++11 -fmodules-cache-path=%t -fmodules -fimplicit-module-maps -I %S/Inputs/submodules-merge-defs %s -verify -fno-modules-error-recovery -fmodules-local-submodule-visibility
6 // RUN: %clang_cc1 -x c++ -std=c++11 -fmodules-cache-path=%t -fimplicit-module-maps -I %S/Inputs/submodules-merge-defs %s -verify -fno-modules-error-recovery -fmodules-local-submodule-visibility -DTEXTUAL -DEARLY_INDIRECT_INCLUDE
7 // RUN: %clang_cc1 -x c++ -std=c++11 -fmodules-cache-path=%t -fmodules -fimplicit-module-maps -I %S/Inputs/submodules-merge-defs %s -verify -fno-modules-error-recovery -fmodules-local-submodule-visibility -fmodule-feature use_defs_twice -DIMPORT_USE_2
|
| auto-module-import.m | 36 // Test umbrella-less submodule includes
40 // Test umbrella-less submodule includes
81 // expected-warning{{missing submodule 'Module.NotInModule'}}
|
| /frameworks/data-binding/compiler/src/test/java/android/databinding/tool/ |
| MockLayoutBinder.java | 26 "com.test.submodule",
|
| /external/clang/docs/ |
| Modules.rst | 113 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.,
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.
219 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.
223 This behavior is currently only approximated when building a module with submodules. 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. This behavior is subject to change.
231 If any submodule of a module is imported into any part of a program, the entire top-level module is considered to be part of the program. As a consequence of this, Clang may diagnose conflicts between an entity declared in an unimported submodule and an entity declared in the current translation unit, and Clang may inline or devirtualize based on knowledge from unimported submodules.
239 * 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.
306 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 *`` (…)
[all...] |
| /external/chromium-trace/catapult/third_party/html5lib-python/html5lib/treebuilders/ |
| __init__.py | 63 # NEVER cache here, caching is done in the dom submodule
72 # NEVER cache here, caching is done in the etree submodule
|
| /external/chromium-trace/catapult/third_party/html5lib-python/ |
| README.rst | 141 as a submodule, thus for git checkouts they must be initialized::
143 $ git submodule init
144 $ git submodule update
|
| /external/clang/include/clang/Basic/ |
| Module.h | 48 /// \brief Describes a module or submodule.
79 /// \brief A mapping from the submodule name to the index into the
80 /// \c SubModules vector at which that submodule resides.
170 /// \brief Whether this is an explicit submodule.
182 /// \brief Whether this is an inferred submodule (module * { ... }).
218 /// \brief The location of the inferred submodule.
308 /// \brief Construct a new module or submodule.
334 /// \brief Determine whether this module is a submodule.
337 /// \brief Determine whether this module is a submodule of the given other
342 /// either because it is a framework module or because it is a submodule
[all...] |
| /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
|
| /prebuilts/go/darwin-x86/src/cmd/go/ |
| vcs_test.go | 51 "hub.jazz.net/git/user1/pkgname/submodule/submodule/submodule",
|
| /prebuilts/go/linux-x86/src/cmd/go/ |
| vcs_test.go | 51 "hub.jazz.net/git/user1/pkgname/submodule/submodule/submodule",
|
| /external/clang/lib/Lex/ |
| PPLexerChange.cpp | 415 // We're done with this submodule.
625 // Just track that we entered this submodule.
645 // Determine the set of starting macros for this submodule; take these
671 // Switch to this submodule as the current submodule.
685 // Create ModuleMacros for any macros defined in this submodule.
689 // Find the starting point for the MacroDirective chain in this submodule.
693 // entered this submodule, but it doesn't really matter.
710 // There's no point doing this if we're tracking local submodule
719 // The latest visibility directive for a name in a submodule affect
[all...] |
| /prebuilts/gdb/darwin-x86/lib/python2.7/test/ |
| pydocfodder.py | 215 submodule = types.ModuleType(__name__ + '.submodule', variable
216 """A submodule, which should appear in its parent's summary""")
|
| /prebuilts/gdb/linux-x86/lib/python2.7/test/ |
| pydocfodder.py | 215 submodule = types.ModuleType(__name__ + '.submodule', variable
216 """A submodule, which should appear in its parent's summary""")
|
| /prebuilts/python/darwin-x86/2.7.5/lib/python2.7/test/ |
| pydocfodder.py | 215 submodule = types.ModuleType(__name__ + '.submodule', variable
216 """A submodule, which should appear in its parent's summary""")
|
