# 游戏引擎编程语言

## glsl

* [OpenGL 4 Reference Pages](https://registry.khronos.org/OpenGL-Refpages/gl4/index.php)
* [GLSL 详解（基础篇） · Colin's Nest](https://colin1994.github.io/2017/11/11/OpenGLES-Lesson04/#attribute_限定符)

## hlsl

* [hlsl sample](https://github.com/microsoft/DirectX-Graphics-Samples/blob/master/Samples/Desktop/D3D12Multithreading/src/shaders.hlsl)
* [HLSL for Vulkan: Resources | Lei.Chat()](https://www.lei.chat/posts/hlsl-for-vulkan-resources/)
* [DirectXShaderCompiler/SPIR-V.rst at main · microsoft/DirectXShaderCompiler](https://github.com/Microsoft/DirectXShaderCompiler/blob/main/docs/SPIR-V.rst#descriptors)
* [Exposing combined image + sampler objects in HLSL · Issue #33 · KhronosGroup/Vulkan-Ecosystem](https://github.com/KhronosGroup/Vulkan-Ecosystem/issues/33)
* [HLSL variable syntax definition](https://topic.alibabacloud.com/a/hlsl-variable-syntax-definition_8_8_32082125.html)
* [Matrix operations for HLSL](https://gist.github.com/mattatz/86fff4b32d198d0928d0fa4ff32cf6fa)
* [StructuredBuffer - Win32 apps | Microsoft Learn](https://learn.microsoft.com/en-us/windows/win32/direct3dhlsl/sm5-object-structuredbuffer)

## Linux

### signal

* [Sebastien Dumetz | Handle linux signals in Unity3D](https://sdumetz.github.io/2017/07/01/handle-unix-signals-unity.html)

### Cuda

* [1. Preface — CUDA C++ Best Practices Guide 12.3 documentation](https://docs.nvidia.com/cuda/cuda-c-best-practices-guide/index.html#)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://okzkx.gitbook.io/blogs/game-tech/languages.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.