Searched refs:definitions (Results 1 – 25 of 36) sorted by relevance
12
18 # This file contains definitions for event log (android.util.EventLog) tags19 # used by Google Mobile Services applications. These definitions are part of26 # missing the tag definitions, and may not be able to show them in their logs.
1 // Build definitions for unit tests.
15 // C++ library for Bluetooth platform wide protobuf definitions
29 const TagDefinition_t* definitions, size_t length) { in buildTagMap() argument32 map.add(definitions[i].tagId, definitions + i); in buildTagMap()
53 // For android_mallopt definitions.
22 // This file contains protobuf definitions used in incidentd directly.
39 // PRODUCT-agnostic resource data like IDs and type definitions.
43 "inconsistent definitions of absolute symbol `%0': old(%1) -> new(%2)",
41 <!-- SECTION: Vulkan type definitions -->177 <!-- SECTION: Vulkan enumerant (token) definitions. -->215 <!-- SECTION: Vulkan command definitions -->224 <!-- SECTION: Vulkan API interface definitions -->262 <!-- SECTION: Vulkan extension interface definitions (none yet) -->
7 - Protocol buffer definitions (.proto files)
51 // The list of types appearing in `oneof` definitions in this type.145 // Enum value definitions.
35 // The messages in this file describe the definitions found in .proto files.73 // All top-level definitions in this file.255 // Each of the definitions above may have "options" attached. These are684 // extend block (possibly containing multiple extension definitions) will
96 // other definitions may be used. Where the mask applies will be
29 # The following would cause duplicate symbol definitions. GPBProtocolBuffers is expected to be
33 // These message definitions are used to exercises known corner cases
251 const TagDefinition_t* definitions, size_t length);
10 conflicting definitions for the same Java constant in Manifest.java. Changed the implementation68 Rewriting these resource IDs to use the package ID 7F while maintaining their definitions under
56 // Resource definitions corresponding to an Android package.246 // as XML attribute values or on the right hand side of style attribute definitions. The concrete
5 enum types in a Ruby DSL. You may write definitions in this DSL directly, but
35 // The messages in this file describe the definitions found in .proto files.68 // All top-level definitions in this file.211 // Each of the definitions above may have "options" attached. These are531 // extend block (possibly containing multiple extension definitions) will
90 …ns as well. Some of these actually work with Protocol Buffers service definitions (defined using …
44 HelpText<"Allow multiple definitions">;
54 * C structure definitions.
294 that the user who changes the contents of definitions files in the296 to use the modified definitions.)