[Plaffy46]

So, I ran into a pretty weird problem with these 2 lines (declared just after the includes as global variables).

new iNumSlots = 3;
new gIsGenuineKillstreaked[MaxClients][iNumSlots];

My own spcomp.exe literally crashes (while it works fine with everything else) when trying to compile this.

Spider compiler gives me these errors :
plugin.sp(7) : error 008: must be a constant expression; assumed zero
plugin.sp(7) : error 009: invalid array size (negative, zero or out of bounds)

What is the actual syntax for declaring 2-dimensional arrays, I tried using handles and stuff, it keeps reporting some weird errors.
I'm pretty sure it's something really stupid, but I was so tired these last days.

[lingzhidiyu]

new gIsGenuineKillstreaked[MAXPLAYERS+1][iNumSlots];

[h3bus]

MaxClients and iNumSlot are variables and not constant.

[Plaffy46]

Well, I knew this was stupid ;_;. Thanks for the help!

[Powerlord]

SourcePawn does have the const keyword, btw.

[Mathias.]

You better use #define NUM_SLOT if you already know his value at the compile time. I doubt that it will change during the run-time since you already define your 2D array size with it and could create a out of bound if you refer to your NumSlot in your loops (if it change). If you want to create dynamic array than it a different story, you will have to look into the ADT_ARRAY from sourcemod docs.

[Powerlord]

Originally Posted by Black-Rabbit You better use #define NUM_SLOT if you already know his value at the compile time. I doubt that it will change during the run-time since you already define your 2D array size with it and could create a out of bound if you refer to your NumSlot in your loops (if it change). If you want to create dynamic array than it a different story, you will have to look into the ADT_ARRAY from sourcemod docs.

Fun fact: a define and a const aren't the same thing. One is a literal replacement of some text everywhere it's used and the other is a type-safe value. Well, as type safe as you can get in Pawn.

Also, I thought the precompiler was eventually going away, meaning that #define would stop working. I can't find a reference to that now, though. If anything, it probably wouldn't be until SM 2.0 and there are apparently plans for at least 1.8 and 1.9 before that happens.

[Mathias.]

precompiler are useful in allot of situation, no way it is going away.

[Mitchell]

Originally Posted by Black-Rabbit precompiler are useful in allot of situation, no way it is going away.

like not needing a variable where you need to loop the elements in an specific array.

[Mathias.]

I don't know where we going with this, the only thing I meant is it preferable to create a precompiler variable instead of a global constant (should never use a global constant in any situations, it doesn't make sense)

EDIT: actually nvm, do what you want. Not like it matter, I'm just trying to hard.