No developer needed, as TechMuc solved the problem. I hope you can formulate his idea without syntax error - otherwise I leave it as a little user quiz.

If I wanted to replace a function with a macro, I would rename it, f.i. wait() to WAIT(), for making clear that it's a macro. But TechMuc's idea is more elegant.

So, Mr Developer...

Are you saying there is no way to do it WITHOUT a plugin?

Or have I missed something TechMuc (or someone else) said?

I guess youneed to fix Techmuc's code.
Haven't actually tried, but maybe this works:

void my_wait_func(var);

my_wait_func = wait; //save pointer of wait in my_wait_func

#define wait(i) do{ diag("waiting\n"); my_wait_func(i); } while(0)

OK...
After MORE wastage of time, re-reading EVERYONES posts in this thread,
I finally got the bastich working! But, by the gods, is it UGLY...

Here it is. IMPORTANT:: The bulk of the code MUST come straight after acknex.h and before any other #include's you do.
Otherwise they will just be processing 'un-redirected' wait functions... I THINK ...


Point of interest for Germanunkol: Be aware that the "engine_gettaskinfo" function
is currently bugged! Check the Bugs forum under Benni003's "engine_getscriptinfo" posting.
This bug also affects the engine_gettaskinfo function too...

Well thank you very much EvilSOB. I now sorta got the macro working.
Sorta, because after the first few wait calls, it always seems to be returning a certain function name - no longer the one which the wait is actually called in.
I suspect this has to do with the wrong behavior of gettaskinfo.

This entirely defeats the purpose of the whole thing, because what I need to do is find out where my text object is overwritten, so I log the name of the current function and the text object's value on every wait call. But if the function name isn't correct, I might as well just not do it.

The only Idea I've had so far is to set a string to a different value after every wait() call (and then log that string), but I'd have to do that manually. Which totally sucks.

Or I'll write a c++ script which does it for me... which might be less horrible, cause I probably have around a thousand functions.

In order to bypass the gettaskinfo bug, I did it by completely removing
the default.c include. Works fine then.

I FIXED IT!
I've been working on this for 6 months and just could not find the bug.
It was - as I've been expecting for quite some time now - an array that was being addressed with a wrong index (resulting in it setting some other part of the memory). By writing a script that added a line before all wait calls, I found out which function it was in. There was some troubles with proc_mode, as those calls changed my results, but I finally found it.

Thanks a lot for all your help!

@Germanunkol: Oh yea, i know those bugs. Once i wrote into the wrong index and destroey something in the background. Resulting in crashes whenever i called a string function >.<

Good to hear.

Its been useful for me too.

Ive been able to write a debug function that can tell me how
long each function is taking to process.

This debug function is also able to filter which functions
get reported on, as well as dumping various global variables
dependant on which function was running during that time.

Its helping to optimise maultiple parallel functions.

But I assume you're using gettaskinfo, right?
I was thinking about writing a similar function, to try and get a higher fps..