bug-autoconf
[Top][All Lists]
Advanced

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

Re: an autotest design flaw


From: Ralf Wildenhues
Subject: Re: an autotest design flaw
Date: Tue, 14 Nov 2006 19:16:32 +0100
User-agent: Mutt/1.5.13 (2006-08-11)

Hello Bruno,

* Bruno Haible wrote on Mon, Nov 13, 2006 at 10:04:47PM CET:
> Ralf Wildenhues wrote:
> > the possibility to use the flexibility of m4
> > is helpful, both for implementing a testsuite environment, and deploying
> > invidividual tests, once you're used to it.
> 
> Details, please? With shell functions, you also have a lot of flexibility.
> You can
>   - define functions depending on the platform (e.g. func_readlink, 
> func_echo),
>   - define variables which expand to shell functions or commands:
>       $echo "abc"
>       $verbose cp ...
> What flexibility do you gain with m4?

Well, there isn't a whole world, once you allow shell functions.  But
for maintaining a repository of shell snippets in m4, you can get some
cheap form of dependency resolution (a la AC_REQUIRE), some literal
value optimization in special cases while maintaining interface
consistency (esp. for some quoting issues this is quite useful), and
typically you can achieve less redundance in the input files: shell
functions are not always the most elegant way to eliminate duplications.

Cheers,
Ralf




reply via email to

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