Macro contents detection about compiler HOT 7 CLOSED

I played with a few methods, it is the "\10;" that causes it, somehow... I actually saw the same bug years ago in fixes.inc, but didn't put the two together:

https://github.com/Y-Less/sa-mp-fixes/blob/90f0e9ba42f8afc7f41241bb1521058bbcf6d9b4/fixes.inc#L8128-L8140

from compiler.

Also possibly related:

#define stock%0\n;%9 stock%0 __stock$
#define iterfunc%0(%1) %0(%1) TYPES:
#define TYPES:%0$ TYPES:

stock iterfunc A(b)
{
}

That hangs the compiler, I don't think it should. My expected output is:

Match stock:

stock iterfunc A(b) __stock${
}

Match iterfunc:

stock A(b) TYPES: __stock${
}

Match TYPES:

stock A(b) TYPES:{
}

No matches left. But it just hangs.

from compiler.

Not sure if it helps, but this is what my macro debugger spits out:

SUBST(test.pwn): 5.0-20 = (28) stock iterfunc A(b) __stock$
SUBST(test.pwn): 5.6-19 = (12)  A(b) TYPES:
SUBST(test.pwn): 5.12-27 = (6) TYPES:
SUBST(test.pwn): 5.12-18 = (6) TYPES:
SUBST(test.pwn): 5.12-18 = (6) TYPES:
SUBST(test.pwn): 5.12-18 = (6) TYPES:
SUBST(test.pwn): 5.12-18 = (6) TYPES:
etc..

BTW, maybe a feature could be added to check if a macro replaces into the same thing then throw an error.

from compiler.

I really wanted your stepper, but it wasm't online. Thanks - that is clearly wrong.

from compiler.

Yeah sorry about that. I've been meaning to improve this and create a pull request here.

from compiler.

OK, I would love to see how much junk gets spit out using that on the YSI test script!

from compiler.

When compiled with "-l" produces "C"

Could this be related to the how -l produces inaccurate results? I remember you brought it up recently.

Gonna close this with "stale" for now as it's either fixed or not a huge problem.

from compiler.