26.11.2018, 16:16
What i would do if that ever happen is to compile the script with this compile option added:
in pawn.cfg (under the pawno directory)
And then search for that unchanged text in the <script-name>.lst file
Not just it give the pre-process output (i.e. caused by #define), but it also give the full path of includes you are using (so you know if it's correct). Sure it doesn't point you directly to which line and which macro/function it caused, but if you compare it to your .pwn script, you'd get a clue where it is.
Код:
-l
And then search for that unchanged text in the <script-name>.lst file
Not just it give the pre-process output (i.e. caused by #define), but it also give the full path of includes you are using (so you know if it's correct). Sure it doesn't point you directly to which line and which macro/function it caused, but if you compare it to your .pwn script, you'd get a clue where it is.