Re: macros, was Looking for volunteers for XL

Kaz Kylheku <kaz@kylheku.com> wrote:
>Problem is, you're creating something akin to an assembly language,
>with instructions that have source and destination operands.


So it looks like... an imperative programming language!


Some typical code:


        int f(struct foo *foo)
        {
...


err = foo_get_bar(foo, q, &bar);
if (err != 0)
...


err = bar_get_box(bar, p, &box);
if (err != 0)
...


...


err = box_frobnz(box, z, &a);
if (err != 0)
...


if (soanso)
{
err = box_grobny(box, y, &b);
if (err != 0)
...
}


...
        }


The version with macros will look exactly the same, except you can omit
the '&', and they're usually upper case.


>The need for generating temporary variables has not gone away.


I think this is not a big deal, since the value is often then used more
than once. Even if not, the code may be more clear, if less concise.
[also helps debugging]

Return to the comp.compilers page.
Search the comp.compilers archives again.