[Hop]

I'm trying to compile this in SourceMod 1.8+, I removed the enum re-tagging since that causes errors but I'm not sure how to redo this part without getting errors, hopefully someone can point me in the right direction, thanks.

PHP Code:

enum
{
String:sName[8],
bool:bEnabled[2],
ConfigSize
};

[...]

any g_aConfig[8][ConfigSize];

[...]

if(g_aConfig[ID][Enabled][Type]) 


PHP Code:

error 001: expected token: ")", but found "["
error 029: invalid expression, assumed zero
warning 215: expression has no effect
error 001: expected token: ";", but found "]"
fatal error 190: too many error messages on one line 


[Fyren]

As far as I know, you can use enums as structs with a newer compiler as long as you declare everything using the older syntax.

Something like your above can't work because your array is literally just "any g_aConfig[8][10]". Trying to throw on another dimension is wrong.

What was the code you used originally?

[Hop]

Originally Posted by Fyren As far as I know, you can use enums as structs with a newer compiler as long as you declare everything using the older syntax. Something like your above can't work because your array is literally just "any g_aConfig[8][10]". Trying to throw on another dimension is wrong. What was the code you used originally?

Before this I was compiling in in 1.6.0 and it was like this:

PHP Code:

enum _:Config
{
    String:Name[8],
    bool:bEnabled[2]
};

[...]

new g_iConfig[8][Config];

[...]

if(g_iConfig[Name][Enabled][ID]) 


[Fyren]

Do you have a reason for tagging the enum itself? It works as I'd expect if you don't.

[Hop]

Originally Posted by Fyren Do you have a reason for tagging the enum itself? It works as I'd expect if you don't.

The tag isn't necessary and that's not what's causing the problem it's trying to access the 2 values in bEnabled, as far as I know it was tagged so it could be used to set the config size.

[Fyren]

With your second snippet but without tagging the enum itself, you can access them as, for example, g_iConfig[0][bEnabled][0] or g_iConfig[0][bEnabled][1]. I have no idea what your "Enabled" or "ID" are since you didn't provide them.

[Hop]

Originally Posted by Fyren With your second snippet but without tagging the enum itself, you can access them as, for example, g_iConfig[0][bEnabled][0] or g_iConfig[0][bEnabled][1]. I have no idea what your "Enabled" or "ID" are since you didn't provide them.

Your values are pretty much what Enabled and ID would be, so now I have added what you said there's 2 tag mismatch and 1 index tag mismatch errors on SetNativeArray. The last one goes away if I use view_as<int> on ConfigSize but I'm not sure if that's right.

PHP Code:

enum Config
{
    String:Name[8],
    bool:bEnabled[2],
    ConfigSize
};

[...]

int iConfig = GetNativeCell(1);
SetNativeArray(2, g_aConfig[iConfig], ConfigSize); 


PHP Code:

warning 213: tag mismatch
warning 229: index tag mismatch (symbol "g_aConfig")
warning 213: tag mismatch 


[Fyren]

You can name your enum starting with a lowercase letter to resolve all three warnings. Uppercase tags warn on implicit conversions, lowercase do not. This (and enums as structs in the first place) are holdovers from the original, upstream Pawn.

[Hop]

Originally Posted by Fyren You can name your enum starting with a lowercase letter to resolve all three warnings. Uppercase tags warn on implicit conversions, lowercase do not. This (and enums as structs in the first place) are holdovers from the original, upstream Pawn.

Awesome, thank you so much.