Re: use of AC_TRY_EVAL broken

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

 



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


_______________________________________________
Autoconf mailing list
Autoconf@xxxxxxx
http://lists.gnu.org/mailman/listinfo/autoconf

[Index of Archives]     [GCC Help]     [Kernel Discussion]     [RPM Discussion]     [Red Hat Development]     [Yosemite News]     [Linux USB]     [Samba]

  Powered by Linux