Re: Keep variable un-expanded in configure script

2011-03-11 Thread Andres Perera
On Fri, Mar 11, 2011 at 2:12 PM, Too, Justin A. wrote: > Thanks for the quick reply, > > ${#} solves the problem -- would this be the best practice? why are you defining a function inside of a macro? > > > Justin > > On 3/11/11 10:37 AM, "Eric Blake" wrote: > >>On 03/11/2011 11:32 AM, Eric Blak

Re: Keep variable un-expanded in configure script

2011-03-12 Thread Andres Perera
On Sat, Mar 12, 2011 at 3:47 AM, Ralf Wildenhues wrote: > Hello Andres, > > * Andres Perera wrote on Fri, Mar 11, 2011 at 10:42:04PM CET: >> why are you defining a function inside of a macro? > > Can't speak for Justin of course, but recent Autoconf itself defines

Re: process result code in if

2013-06-07 Thread Andres Perera
On Thu, Jun 6, 2013 at 8:11 AM, Eric Blake wrote: > - Original Message - > >> >> A more robust, (and more portable), formulation may be: >> >> echo $var | grep '^+\{0,1\}[0-9]\{1,\}$' > /dev/null 2>&1 > > Why fork, when straight shell will do? yea, forking for grep is probably going to