| /prebuilts/clang/host/linux-x86/clang-3960126/tools/scan-build/bin/ |
| scan-build | [all...] |
| /prebuilts/clang/host/linux-x86/clang-3977809/tools/scan-build/bin/ |
| scan-build | [all...] |
| /prebuilts/clang/host/linux-x86/clang-4053586/tools/scan-build/bin/ |
| scan-build | [all...] |
| /prebuilts/misc/darwin-x86/analyzer/tools/scan-build/ |
| scan-build | 1060 created as needed to represent separate "runs" of the analyzer. If this
[all...] |
| /prebuilts/misc/linux-x86/analyzer/tools/scan-build/ |
| scan-build | 1060 created as needed to represent separate "runs" of the analyzer. If this
[all...] |
| /prebuilts/gdb/darwin-x86/lib/python2.7/pydoc_data/ |
| topics.py | 11 'bltin-code-objects': '\nCode Objects\n************\n\nCode objects are used by the implementation to represent "pseudo-\ncompiled" executable Python code such as a function body. They differ\nfrom function objects because they don\'t contain a reference to their\nglobal execution environment. Code objects are returned by the built-\nin ``compile()`` function and can be extracted from function objects\nthrough their ``func_code`` attribute. See also the ``code`` module.\n\nA code object can be executed or evaluated by passing it (instead of a\nsource string) to the ``exec`` statement or the built-in ``eval()``\nfunction.\n\nSee *The standard type hierarchy* for more information.\n',
14 'bltin-type-objects': "\nType Objects\n************\n\nType objects represent the various object types. An object's type is\naccessed by the built-in function ``type()``. There are no special\noperations on types. The standard module ``types`` defines names for\nall standard built-in types.\n\nTypes are written like this: ``<type 'int'>``.\n",
[all...] |
| /prebuilts/gdb/linux-x86/lib/python2.7/pydoc_data/ |
| topics.py | 11 'bltin-code-objects': '\nCode Objects\n************\n\nCode objects are used by the implementation to represent "pseudo-\ncompiled" executable Python code such as a function body. They differ\nfrom function objects because they don\'t contain a reference to their\nglobal execution environment. Code objects are returned by the built-\nin ``compile()`` function and can be extracted from function objects\nthrough their ``func_code`` attribute. See also the ``code`` module.\n\nA code object can be executed or evaluated by passing it (instead of a\nsource string) to the ``exec`` statement or the built-in ``eval()``\nfunction.\n\nSee *The standard type hierarchy* for more information.\n',
14 'bltin-type-objects': "\nType Objects\n************\n\nType objects represent the various object types. An object's type is\naccessed by the built-in function ``type()``. There are no special\noperations on types. The standard module ``types`` defines names for\nall standard built-in types.\n\nTypes are written like this: ``<type 'int'>``.\n",
[all...] |
| /prebuilts/python/darwin-x86/2.7.5/lib/python2.7/pydoc_data/ |
| topics.py | 11 'bltin-code-objects': '\nCode Objects\n************\n\nCode objects are used by the implementation to represent "pseudo-\ncompiled" executable Python code such as a function body. They differ\nfrom function objects because they don\'t contain a reference to their\nglobal execution environment. Code objects are returned by the built-\nin ``compile()`` function and can be extracted from function objects\nthrough their ``func_code`` attribute. See also the ``code`` module.\n\nA code object can be executed or evaluated by passing it (instead of a\nsource string) to the ``exec`` statement or the built-in ``eval()``\nfunction.\n\nSee *The standard type hierarchy* for more information.\n',
14 'bltin-type-objects': "\nType Objects\n************\n\nType objects represent the various object types. An object's type is\naccessed by the built-in function ``type()``. There are no special\noperations on types. The standard module ``types`` defines names for\nall standard built-in types.\n\nTypes are written like this: ``<type 'int'>``.\n",
[all...] |
| /prebuilts/python/linux-x86/2.7.5/lib/python2.7/pydoc_data/ |
| topics.py | 11 'bltin-code-objects': '\nCode Objects\n************\n\nCode objects are used by the implementation to represent "pseudo-\ncompiled" executable Python code such as a function body. They differ\nfrom function objects because they don\'t contain a reference to their\nglobal execution environment. Code objects are returned by the built-\nin ``compile()`` function and can be extracted from function objects\nthrough their ``func_code`` attribute. See also the ``code`` module.\n\nA code object can be executed or evaluated by passing it (instead of a\nsource string) to the ``exec`` statement or the built-in ``eval()``\nfunction.\n\nSee *The standard type hierarchy* for more information.\n',
14 'bltin-type-objects': "\nType Objects\n************\n\nType objects represent the various object types. An object's type is\naccessed by the built-in function ``type()``. There are no special\noperations on types. The standard module ``types`` defines names for\nall standard built-in types.\n\nTypes are written like this: ``<type 'int'>``.\n",
[all...] |
| /external/google-breakpad/ |
| configure | [all...] |
| /external/liblzf/ |
| configure | [all...] |
| /toolchain/binutils/binutils-2.25/libiberty/ |
| configure | [all...] |
| /prebuilts/go/darwin-x86/src/cmd/link/internal/ld/ |
| dwarf.go | 699 // Construct type to represent an array of BucketSize keys
713 // Construct type to represent an array of BucketSize values
[all...] |
| /prebuilts/go/darwin-x86/src/math/big/ |
| float.go | 32 // represent the value. The rounding mode specifies how a result should
205 // MinPrec returns the minimum precision required to represent x exactly
[all...] |
| /prebuilts/go/linux-x86/src/cmd/link/internal/ld/ |
| dwarf.go | 699 // Construct type to represent an array of BucketSize keys
713 // Construct type to represent an array of BucketSize values
[all...] |
| /prebuilts/go/linux-x86/src/math/big/ |
| float.go | 32 // represent the value. The rounding mode specifies how a result should
205 // MinPrec returns the minimum precision required to represent x exactly
[all...] |
| /compatibility/cdd/7_hardware-compatibility/ |
| 7_4_data-connectivity.md | 237 declare the `android.hardware.nfc` feature as the classes represent a
|
| /external/antlr/antlr-3.4/runtime/Delphi/Sources/Antlr3.Runtime/ |
| Antlr.Runtime.Tree.pas | 418 /// As we flatten the tree, we use UP, DOWN nodes to represent
532 /// an empty node whose children represent the list. An empty, but
[all...] |
| /external/protobuf/js/binary/ |
| decoder.js | 37 * Major caveat - Javascript is unable to accurately represent integers larger
|
| utils.js | 456 // base-2 to base-1e7, which allows us to represent the 64-bit range with
|
| /external/testng/doc/ |
| prettify.js | 107 /** a chunk of text with a style. These are used to represent both the output
[all...] |
| /external/v8/benchmarks/ |
| deltablue.js | 151 * to represent a constraint.
|
| /prebuilts/go/darwin-x86/src/cmd/compile/internal/gc/ |
| dcl.go | 32 // represent object names. Sym is just a convenient type for saving shadowed
|
| /prebuilts/go/darwin-x86/src/encoding/asn1/ |
| asn1.go | 214 // Equal reports whether oi and other represent the same identifier.
|
| /prebuilts/go/darwin-x86/src/encoding/gob/ |
| encoder_test.go | 462 // Now follow various tests that decode into things that can't represent the
|
