[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: use of AC_TRY_EVAL broken
From: |
Ralf Wildenhues |
Subject: |
Re: use of AC_TRY_EVAL broken |
Date: |
Sat, 25 Oct 2008 11:17:06 +0200 |
User-agent: |
Mutt/1.5.18 (2008-05-17) |
Hi Bruno,
* Bruno Haible wrote on Fri, Oct 24, 2008 at 11:28:06PM CEST:
> Ralf Wildenhues wrote:
> > a suggestion for a new name: AC_EVAL_IFELSE.
>
> There's actually two cases to consider, if you want to make it easy to use
> for the developer:
> - the case of a command that should be executed and logged,
> - the case of a variable that contains a command that should be executed and
> logged,
>
> If the second one is AC_EVAL_IFELSE, what would be the name of the first one
> (without EVAL)?
Actually, I suggest AC_EVAL_IFELSE for the first one, because it
involves the shell "eval"uating a command. The second one can just
use AC_EVAL_IFELSE([$command], ...), no?
Anyway writing such a beast to be robust is going to be some work ...
Cheers,
Ralf