[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: I think binary-branch is almost ready for play time

From: Alexandre Oliva
Subject: Re: I think binary-branch is almost ready for play time
Date: 14 May 2001 00:46:46 -0300
User-agent: Gnus/5.090002 (Oort Gnus v0.02) XEmacs/21.1 (Cuyahoga Valley)

On May 13, 2001, Bruce Korb <address@hidden> wrote:

> Alexandre Oliva wrote:
>> > In other words, your new macro should not need to do this:
>> >    [= test-and-exit  test = (get "test")  ...  =]
>> > because it would be redundant.
>> Good.  But I had meant to write ``I'd like *you* to implement ...''
>> :-)

> Then I would need to understand better what you wanted to have
> happen.

I just need one macro implemented in terms of another.  The idea was
that test-OR-exit would call test with the same condition, and append
to the else clause the commands to output the error message and the
exit command.  Or something like that.

>    [= test-OR-exit  msg = "start-[= gather-the-message =]-end" =]

> is now accepted.  What happens is that the string "sta...end"
> is gathered up at load time.  When this invocation fires,
> an "anonymous template" is created with that text and then processed.
> The output is redirected to an unlinked file (no Windows here),
> and read back in.

This won't help much in this case (but it was indeed one of the major
requirements for AutoGen to be usable here).  What I need is the
definition of test-OR-exit to refer to other macros.

> I would not nest macros, I would add an argument, and
> maybe some sanity checks thus:

The issue is not about how to implement test, it's about how to
implement macros in terms of others.

Alexandre Oliva   Enjoy Guarana', see
Red Hat GCC Developer                  address@hidden,}
CS PhD student at IC-Unicamp        address@hidden,}
Free Software Evangelist    *Please* write to mailing lists, not to me

reply via email to

[Prev in Thread] Current Thread [Next in Thread]