Stanislav Gromov

> Basically, just map this: > > ```pawn > native Tag.Function(a, b); > stock Tag.Function(a, b) > { > } > ``` > > To this > > ```pawn >...

> These are some very good ideas, but regardless of the implementation there's still one major issue with this idea - pre-processor function hooking just doesn't work. The defines would...

Cleaned up the code and added a few workarounds to support detection of uninitialized arrays (previously the compiler was able to detect only single variables). I also made the compiler...

> It would be much easier to blacklist uses, rather than whitelist them. I don't think there are any others besides these: if (uninitialised) // warning FuncNotPassedByRef(uninitialised) // warning lvalue...

But still, not everyone uses sampctl or manually installs modified includes from that repo. Also, warning 239 was disabled for native functions for the same reason: https://github.com/pawn-lang/compiler/commit/8948f207ea9c7cef4e7808751a499310d1407148

> Yes, another warning did the same, before we fixed the includes. Err... no, it did so *after* the includes were fixed. The last const-correctness fix was merged on 17...

Must be due to a workaround I used for arrays (which I had to add because function `address()` from `sc4.c` marks arrays as `uWRITTEN` on all types of access, even...

> https://github.com/pawn-lang/YSI-Includes/blob/771b7b027cad95da1ec4210b9791eddf7b3b97d3/YSI_Core/y_core/y_utils_impl.inc#L923-L931 > https://github.com/pawn-lang/YSI-Includes/blob/771b7b027cad95da1ec4210b9791eddf7b3b97d3/YSI_Core/y_core/y_core_entry.inc#L172-L187 > https://github.com/pawn-lang/YSI-Includes/blob/771b7b027cad95da1ec4210b9791eddf7b3b97d3/YSI_Data/y_bit/y_bit_impl.inc#L232-L242 I made the compiler not issue warning 210 if a variable is incremented or decremented with `++`/`--`, but in all of the abovementioned cases...

> Maybe it should be restricted only to variables whose first use is a read outside of a loop in which they are modified. Sounds doable, but I'll need #533...

While I like this idea (and would love to try implementing it when #234 is done), the draft itself definitely needs a few corrections. > ``` > /* static */...