[Resolved] Tag mismatch warnings (expected tag "bool", but found none)

[rt-2]

Hi, When I use AddStaticVehicleEx it gives me this warning:

C:\Users\rt-2\Desktop\SAARP\SAMP\pawno\include\nex-ac.inc(2080) : warning 213: tag mismatch: expected tag "bool", but found none ("_")

this is the code that triggers the warning, if I remove this particular function from that line, the warning disappear:

new vehicleid = AddStaticVehicleEx(strval(vehid), floatstr(pos_x), floatstr(pos_y), floatstr(pos_z), floatstr(pos_angle), strval(color1), strval(color2), -1, addsiren);

• addsiren is an int.
• AC version is v1.9.56

Thank you, rt-2

EDIT: Solution is to ignore the warning, this is still stable because bitwise, bool will act the same as int.

[NexiusTailer]

'addsiren' is an int in default sa-mp includes too, but if you use latest YSI (or any other libraries, idk exactly what else behaves the same for now) - you'll see such warnings. Regarding the problem itself, most likely such scripts also hooks some natives and modify their arguments in accordance with how it is possible now declared in the modified samp includes, thereby creating these compilation problems.

So, there is nothing I could do about it if we say in the context of the fact that anticheat still primarily supports standard (canonical) samp includes, and not modified ones. I think this is a problem with YSI and all similar scripts, which are increasingly starting to have problems with the default compiler/includes over time, although they fully supported them before.

[NexiusTailer]

UPD: Current y_iterate have exactly what I've mentioned, here. Probably you use that?

[rt-2]

UPD: Current y_iterate have exactly what I've mentioned, here. Probably you use that?

So basically I should set addsiren to a bool instead of int simply?

[NexiusTailer]

This should be changed to int in y_iterate to be a real solution (at least when default includes detected). Otherwise there still can be warnings on anticheat's hook of AddStaticVehicleEx.

[rt-2]

Should we go around the problem and detect when YSI is included for kind of a solution even if not perfect?

[NexiusTailer]

The problem in that not just YSI can use such custom tags for those params in its hooks and it's pretty predictable in this way in the future, if it would be necessary to do exclusionary checks for a bunch of scripts that might be included with such style too.

The real solution to the problem is a return (and making sure that it does not break in the future by testing) support for default samp includes in libraries such as y_iterate and similar, thereby they will stop creating such problems ever again.

[rt-2]

Anyway Im guessing for int and bool, true and false will just be the same bit-wise than the int 1/0 so we can ignore this and assume everything is stable? Thank you

[NexiusTailer]

Yeah, this continues to be stable as well as it continues to be stable with const-correctness warnings from the new compiler/includes. The only problem is the presence of these warnings and the fact that the user has to see them if he use YSI or modified samp includes.

[rt-2]

Ok thank you.