Item IDs aren't checked for capitalisation

[nemethviktor]

A little more context on discord https://discord.com/channels/142724111502802944/337701432230805505/1506201143842181260 but basically if I define the ID list as

// Unit Wagons (Rail), available ID range: 13000-13001 (hex 0x32C8..0x32C9)
#define ID_RANGE_UNIT_WAGONS_RAIL 0x32C8..0x32C9
item(FEAT_TRAINS, item_mu_MU_Wagon_Unpowered, 13000) {}
item(FEAT_TRAINS, item_mu_MU_Wagon_Powered, 13001) {}

note non-lowercase above

but then define the individual item lowercase

item(FEAT_TRAINS, item_mu_mu_wagon_unpowered) {
    property {
        name: string(str_mu_mu_wagon_unpowered);
        

then the nml will compile without error but will cause silent failures in switches that depend on vehicle ids such as attachment rules.

[PeterN]

Sounds like "inconsistent case-sensitivity".

[PeterN]

Probably not even inconsistent sensitivity.

• item_mu_MU_Wagon_Unpowered is explicitly defined as a static ID.
• item_mu_mu_wagon_unpowered is implicitly defined as a dynamic ID.

Two IDs are defined and both are valid in switches, but of course mayn't do what you intended.

So (without having checked the code) possibly this becomes a feature request: make IDs case-insensitive. The spec, afaics, does not mention either way.