Le_Forgeron <jgr### [at] freefr> wrote:

> Do not see macro as a function calls, but as text substitution.
>
> It might help.

Thanks Jerome - it does help - sometimes, but it still gets complicated as the
contents of the macro get larger and more complex.

I'd still like to see a few working code examples that would act as a good
reference source when trying to write and debug my own macros.

THIS you can do, THAT you can't - really helps to demonstrate it, rather than
general, generic "explanations" like in the documentation.

"Seeing" what makes or breaks a chunk code helps in having that "a-HA!" moment
that's so often needed.

Post a reply to this message