Stanislav Gromov

Speaking of fixing warnings, it would be good to remove a trailing comma in amx.h at the end of the AMX_ERR_\* enumeration. https://github.com/compuphase/pawn/blob/e46e3ba97980c196e9a4e4a33ddb60993a5d2d24/amx/amx.h#L380 Because of that comma both g++ and...

> For valstr, that would be a code-breaking change (the change could stop code compiling) You mean for `emit`-related code or for "regular" code? > That's also really a programmer...

Don't want to sound rude, but is it really a good idea to use MPL 2.0 instead of a more simple license like BSD, MIT or zlib? I mean I...

> The source must be "made available", that's not the same thing as "sent" It doesn't only say "made available". >http://directory.fsf.org/wiki/License:MPLv2.0 > 3.2. Distribution of Executable Form > > If...

I think a proper explanation is that properties in Pawn weren't designed for running more than one script at a time. What happens is that when a script (and by...

> what about having 1-199 be normal errors and 200+ be fatal? The range of 200+ is already occupied by warning IDs - changing them would break a lot of...

>What happened to bits 1-5? Nowhere are those bits used as far as I could check. Maybe they were never even been used because they were supposed to be reserved...

## inconsistent naming of preprocessor tokens Just noticed that the constant for the `#include` directive is defined as `tINCLUDE`, with a `t` prefix, while the names of the other directive-related...

## unused error IDs Error IDs `11` ("invalid outside functions") and `210` ("possible use of symbol before initialization") don't seem to be used anywhere within the compiler. I even searched...

Just stumbled upon this tiny piece of code in function `funcstub()` (`sc1.c`): ```C sym->usage=(char)(uNATIVE | uRETVALUE | uDEFINE | (sym->usage & uPROTOTYPED)); ``` Note that the assigned value is casted...