Welcome to the ZDoom Forums!

Huh, I remember that I reported it. Or I wanted to report it? Or that was on another forum?
Hmmmm, something really wrong with this reality. Time to jump to another dimension, before something bad happ

[quote="Player701"]Is one of the developers a time traveler? :o :P[/quote]
We all are. It's a perk. :twisted:

So's the Tardis but we keep those well hidden.

Also see [url=https://forum.zdoom.org/viewtopic.php?f=7&t=60500]here[/url] for a similar report regarding arrays of names, which was for some reason closed as "Duplicate" without any further remarks. Is one of the developers a time traveler? :o :P

Most likely this is an oversight in the type checking system. TEchnically casting between int and TextureID should be safe, it's just a type safe wrapper around an index.

array<TextureID> b;
TextureID t = TexMan.checkForTexture("titlepic", TexMan.Type_Any);

b.push(t);

b.push(int(t));

Consider the code:[code]array<TextureID> b;
TextureID t = TexMan.checkForTexture("titlepic", TexMan.Type_Any);[/code]
Straightforward attempt to populate the array won't succeed:
[code]b.push(t);[/code]Running a mod with such code results in error: "Numeric type expected, got a name".

However, casting TextureID to int works:
[code]b.push(int(t));[/code]

So, it's possible to create an array of TextureIDs but it's impossible to fill it without type casting. This is inconvenient and looks hacky.

Questions:
1. Is a bug or ZScript limitation?
2. If it's a ZScript limitation, is it safe to cast TextureID to int? I see that C++ TextureID counterpart, FTextureID, consists of a single int, so for now type casting is probably safe. Will it remain so?

Runnable example:[attachment=0]textureid-array.pk3[/attachment]