Re: Looking for volunteers for XL

Kaz Kylheku <kaz@kylheku.com> wrote:
>For one thing, any syntactic unit that contains declarations cannot be
>an expression that returns a value. Macros that need to generate
>complex code that requires hidden variables automatically have a
>difficulty in returning a value in a function-call-like way, because
>only expressions do that.


That is valid, but it's not not-difficulty work-around-ed.


#2. Don't use function-like macros.


Make the result one of the parameters (unless it is really simple, then
some day in the future your 'really simple' macro is not so really
simple).


e.g.


        #define GET_FORDO_BIT(FOP) \
        ...


        int f(int x)
        {
...
if (GETFORDO_BIT(fop))
{
...
}
...
        }


versus


        #define GET_FORDO_BIT(FOP, FOB) \
        ...


        int f(int x)
        {
...
GET_FORDO_BIT(fop, fob);
if (fob)
{
...
}
...
        }


How hard is that?

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