GDExtension API: Modulo operator’s enum is misnamed OP_MODULE

[ParadoxV5]

Godot version

as early as 3.1 – 4.0.2

System information

GDExtension (also applies to GDNative)

Issue description

Moved and elaborated from godotengine/godot-headers#105

The modulo operator’s enum in GDExtension/GDNative is named OP_MODULE rather than OP_MODULO.

C header:

godot/core/extension/gdextension_interface.h

Line 119 in 9f12e7b

GDEXTENSION_VARIANT_OP_MODULE,

API JSON: https://github.com/ParadoxV5/godot-headers/blob/732ed57b5f19583a7af4272e58ce509d5ff58586/extension_api.json#L3985

• If this is not intended, a change for the next minor patch is much appreciated.
• If this is intentional (e.g., header naming limitation), please document the reason either near the header line or on Godot docs and link.
• If this is not intended but was left as is simply for backward compatibility, then it’s unfortunate that the Godot 4.0 overhaul overlooked it, but it deserves consideration for the hypothetical future version 5.0. (I searched the tracker with the keyword ‘modulo’ already and there wasn’t a previous issue for project tracking.)

Steps to reproduce

• C header: check the core/extension/gdextension_interface.h file at around line 119
• API JSON: generate the file and look at around line 3985

Minimal reproduction project

N/A

[Calinou]

If this is not intended but was left as is simply for backward compatibility, then it’s unfortunate that the Godot 4.0 overhaul overlooked it, but it deserves consideration for the hypothetical future version 5.0. (I searched the tracker with the keyword ‘modulo’ already and there wasn’t a previous issue for project tracking.)

• See Add a backwards-compatibility system for GDExtension #76446.

[ParadoxV5]

it’s unfortunate that the Godot 4.0 overhaul overlooked it

Just came across #16863. OP_MODULE ➡ OP_MODULO is not on final list.

[akien-mga]

The GDExtension API reflects what's in the core Variant API:

godot/core/variant/variant.h

Line 522 in 116f783

OP_MODULE,

Changing this would break compatibility, which we don't want to do before Godot 5 unless it's absolutely needed to fix critical issues. This slight misnomer doesn't seem critical to fix now.

[ParadoxV5]

Changing this would break compatibility, which we don't want to do before Godot 5 unless it's absolutely needed to fix critical issues. This slight misnomer doesn't seem critical to fix now.

If this is not intended but was left as is simply for backward compatibility, then it’s unfortunate that the Godot 4.0 overhaul overlooked it, but it deserves consideration for the hypothetical future version 5.0. (I searched the tracker with the keyword ‘modulo’ already and there wasn’t a previous issue for project tracking.)