On 2012-11-07 15:08, deadalnix wrote: > This is nice, but lack the possible to explore the internal of the > function and to surgery in it :D > > Still a step forward. I'm not entirely sure I understand. Do you mean that you won't see the output of the macro? In that case the compiler should have a flag for outputting the result of a macro. -- /Jacob Carlborg