Lines Matching refs:compatibility

11 This chapter describes how Vulkan is versioned, how compatibility is
12 affected between different versions, and compatibility rules that are
137 <<extendingvulkan-compatibility-coreversions>>
466 In order to maintain compatibility with implementations released prior to
471 compatibility with applications written to work with the previous
529 However, for compatibility, only an empty list of layers or a list that
753 If a required extension has been <<extendingvulkan-compatibility-promotion,
785 [[extendingvulkan-compatibility-coreversions]]
789 versions>> of the Vulkan specification provide different compatibility
842 <<extendingvulkan-compatibility-obsoletion>> for more information.
849 removal of <<extendingvulkan-compatibility-deprecation,deprecated
861 that will necessarily require breaking compatibility.
873 [[extendingvulkan-compatibility-extensions]]
890 <<extendingvulkan-compatibility-obsoletion, made obsolete>> by either a core
895 [[extendingvulkan-compatibility-promotion]]
915 compatibility, however it should require little effort to port code from the
919 as either <<extendingvulkan-compatibility-deprecation, deprecated>> or
920 <<extendingvulkan-compatibility-obsoletion, obsoleted>> as appropriate, and
927 When an extension is promoted, any backwards compatibility aliases which
940 is a backwards compatibility alias that exists only due to a naming mistake
945 [[extendingvulkan-compatibility-deprecation]]
957 guarantees of compatibility, and applications may require drastic
966 [[extendingvulkan-compatibility-obsoletion]]
978 [[extendingvulkan-compatibility-aliases]]
990 application with no compatibility issues.
1010 [[extendingvulkan-compatibility-specialuse]]