autoconf
[Top][All Lists]
Advanced

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

Re: problem with ifelse


From: Vincent Torri
Subject: Re: problem with ifelse
Date: Thu, 5 Mar 2009 23:43:22 +0100 (CET)



On Thu, 5 Mar 2009, Eric Blake wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to Vincent Torri on 3/4/2009 1:34 PM:

dnl use: ECORE_CHECK_MODULE(Foo, default-enabled[, dependancy[,
ACTION-IF-FOUND[, ACTION-IF-NOT-FOUND]]])
AC_DEFUN([ECORE_CHECK_MODULE],
[
pushdef([UP], translit([$1], [a-z], [A-Z]))dnl
pushdef([DOWN], translit([$1], [A-Z], [a-z]))dnl

Consider using the m4sugar namespace.  We have threatened to add warnings
when using the raw m4 namespace from within configure scripts, because it
is too easy to run into conflicts.  For that matter, why not use
m4_toupper and m4_tolower, instead of rewriting them yourself?  Not to
mention that those macros are more robust to arguments that include
potential macro names (your version is underquoted, and would end up
expanding such a macro).

m4_pushdef([UP], m4_toupper([[$1]]))dnl

and what to do with m4_pushdef if i want to transform - to _. For example, I use this:

pushdef([UP], translit([$1], [-a-z], [_A-Z]))dnl
pushdef([DOWN], translit([$1], [-A-Z], [_a-z]))dnl

Vincent Torri




reply via email to

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