Home
last modified time | relevance | path

Searched refs:naming (Results 1 – 25 of 547) sorted by relevance

12345678910>>...22

/third_party/googletest/googletest/src/hwext/
Dgtest-tag.cc34 printf("%s--gtest_%s=(", indents[0], naming()); in printHelp()
57 sprintf(err, "Illegal %s value '0x%08x'\n", naming(), hex); in verify()
88 const string ele_full_name_string = string(naming()) + "." + ele_name; in eleForName()
97 fprintf(stderr, "Unrecognized %s value '%s'\n", naming(), pch); in eleForName()
187 if (!compareStringsByIgnoreCase(set_name, set->naming())) { in flagForName()
/third_party/vk-gl-cts/external/vulkan-docs/src/style/
Dnaming.txt5 [[naming]]
9 follow a set of naming rules, providing a consistent scheme for developers.
26 Vulkan working group, and be added to the <<naming-abbreviations,Common
27 Abbreviations>> and <<naming-prefixes,Standard Prefixes>> sections,
50 [[naming-preprocessor]]
66 <<extensions-naming-conventions-name-strings,extension name string
99 This rule applies to all type definitions except <<naming-funcpointers,
129 [[naming-extension-structures]]
134 Currently there are two examples of such naming schemes.
137 structure should use this naming scheme:
[all …]
Dnaming.adoc5 [[naming]] anchor
9 follow a set of naming rules, providing a consistent scheme for developers.
26 Vulkan working group, and be added to the <<naming-abbreviations,Common
27 Abbreviations>> and <<naming-prefixes,Standard Prefixes>> sections,
50 [[naming-preprocessor]]
66 <<extensions-naming-conventions-name-strings,extension name string
99 This rule applies to all type definitions except <<naming-funcpointers,
129 [[naming-extension-structures]]
134 Currently there are two examples of such naming schemes.
137 structure should use this naming scheme:
[all …]
Drevisions.adoc21 chapter from `styleguide.adoc` and make anchor naming scheme consistent.
170 * 2017-10-15 - Add more details of <<extensions-naming-author-IDs, `KHX`
189 * 2017-03-19 - Add naming rule for <<naming-extension-structures, Extension
218 Vulkan API Specification and merge content with the naming guide.
219 Put extension and naming chapters into their own source files.
220 * 2016-06-20 - Add API naming guide.
Dintroduction.adoc44 * <<naming,API Naming Conventions>> - the required rules for choosing
54 language use, API naming conventions, common words and phrases to use
/third_party/vk-gl-cts/external/vulkan-docs/src/appendices/
DVK_EXT_debug_marker.adoc22 It introduces concepts of object naming and tagging, for better tracking of
64 Annotating regions of a workload with naming information so that offline
138 renaming, prevents late binding of naming information, and does not allow
139 naming of implicitly created objects such as queues and swapchain images.
DVK_EXT_debug_marker.txt22 It introduces concepts of object naming and tagging, for better tracking of
64 Annotating regions of a workload with naming information so that offline
138 renaming, prevents late binding of naming information, and does not allow
139 naming of implicitly created objects such as queues and swapchain images.
DVK_EXT_video_decode_h264.txt37 naming conventions.
DVK_KHR_video_queue.txt36 `VkVideoCapabilityFlagsKHR`, following Vulkan naming conventions.
DVK_EXT_video_encode_h264.txt41 `VkVideoEncodeH264CapabilityFlagsEXT`, following Vulkan naming
/third_party/vk-gl-cts/external/vulkan-docs/src/
Dstyleguide.txt72 * <<naming,API Naming Conventions>> - the required rules for choosing
82 language use, API naming conventions, common words and phrases to use
160 include::style/naming.txt[]
320 * 2017-10-15 - Add more details of <<extensions-naming-author-IDs, `KHX`
339 * 2017-03-19 - Add naming rule for <<naming-extension-structures, Extension
368 Vulkan API Specification and merge content with the naming guide.
369 Put extension and naming chapters into their own source files.
370 * 2016-06-20 - Add API naming guide.
Dstyleguide.adoc39 include::{style}/naming.adoc[]
/third_party/rust/crates/clap/tests/derive/
Dmain.rs22 mod naming; module
/third_party/libinput/quirks/
DREADME.md19 Data file naming
29 This is not a fixed naming scheme and may change at any time. It's an
/third_party/openGLES/extensions/AMD/
DAMD_occlusion_query_event.txt263 the naming conventions of object state getters already, as
271 Option (a) follows the existing naming convention of the query object
273 Option (b) follows the naming convention of other object types, but
277 Option (c) doesn't follow either the naming convention of the query
/third_party/unity/docs/
DThrowTheSwitchCodingStandard.md52 Let's talk about naming things. Programming is all about naming things. We name
57 When naming things, we follow this hierarchy, the first being the
89 naming. We find i, j, and k are better loop counters than loopCounterVar or
/third_party/cJSON/tests/unity/docs/
DThrowTheSwitchCodingStandard.md52 Let's talk about naming things. Programming is all about naming things. We name
57 When naming things, we more or less follow this hierarchy, the first being the
90 naming. We find i, j, and k are better loop counters than loopCounterVar or
/third_party/skia/third_party/externals/opengl-registry/extensions/AMD/
DAMD_occlusion_query_event.txt263 the naming conventions of object state getters already, as
271 Option (a) follows the existing naming convention of the query object
273 Option (b) follows the naming convention of other object types, but
277 Option (c) doesn't follow either the naming convention of the query
/third_party/flutter/glfw/src/
DCMakeLists.txt90 # Add a suffix to the import library to avoid naming conflicts
93 # Add a suffix to the import library to avoid naming conflicts
/third_party/libbpf/docs/
Dlibbpf_naming_convention.rst3 API naming convention
7 functions and types. Every group has its own naming convention
68 API documentation above. See API naming convention to choose the right
/third_party/toybox/www/
D0bsd-mckusick.txt49 Subject: Re: License naming question.
66 > Subject: License naming question.
131 > thought of the naming confusion, and I wrote two long things on my
/third_party/flutter/glfw/docs/
Dinternal.dox8 responsibility and its own naming conventions.
18 The public interface uses the OpenGL naming conventions except with GLFW and
/third_party/googletest/googletest/include/gtest/hwext/
Dgtest-tag.h49 const char* naming() const { return name; } in naming() function
/third_party/gstreamer/gstplugins_base/gst-libs/gst/riff/
Dmeson.build41 # This library does not respect the type naming conventions required to be
/third_party/openssl/crypto/objects/
DREADME.md4 To cover all the naming hacks that were previously in `objects.h` needed some

12345678910>>...22