Lines Matching refs:naming
5 [[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:
155 should use this naming scheme:
281 These commands fall into two categories from a naming perspective:
353 [[naming-funcpointers]]
405 ** The slightly odd naming prevents it clashing with any future variables.
458 [[naming-extension-identifiers]]
464 <<extensions-naming-conventions,Extension and Layer Naming Conventions>>
491 [[naming-extension-enumerant-names]]
542 [[naming-abbreviations]]
611 [[naming-prefixes]]