Inconsistent Naming Conventions in Generated Code

[code-with-parth]

Description:
The translator occasionally produces output shaders with inconsistent or non-standard naming conventions for variables, functions, and other identifiers. This can lead to conflicts or reduce readability, especially when integrating the translated shaders into larger projects.

Steps to Reproduce:

1. Write an HLSL shader with complex variable names or function declarations.

2. Translate the shader using CrossGL.

3. Review the generated output and observe inconsistencies in naming.

Expected Behavior:
The translator should adhere to a consistent and configurable naming convention that aligns with standard practices in shader development.

Actual Behavior:
The output contains inconsistent naming styles, such as mixed camelCase, snake_case, and PascalCase, or unnecessarily modified identifiers.

Environment Details:

OS: Windows 11

DirectX Version: 11

Python Version: 3.9

Additional Context:

This issue impacts maintainability and integration of the translated shaders.

A potential fix could include adding a configurable naming convention option in the translator settings.

[code-with-parth]

@CrossGL-issue-bot assign me