gcc (which you could use even if the c++ source was written for a different compiler) called with -E will preprocess all your macros and write the resulting source code to standard output. And maybe the compiler you use has a similar parameter
UPDATE: About your profiling problem: You might try to insert a print "$name\n" statement into the loop and watch the output to see if the time is wasted in every loop or if there are specific macros that waste a lot of time. My (wild, unsubstantiated) guess would be the loop regex because the profiler might have problems pinpointing the time wasted in loop expressions. Also regexes can waste a lot of time if they need to backtrack a lot. I can see that your loop regex has to backtrack when it gets to the last line of a regex, but that shouldn't be enough for the delay you are seeing
In reply to Re: define analyser - performance problem
by jethro
in thread define analyser - performance problem
by grizzley
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |