[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: m4sh bug (AS_VAR_IF)
From: |
Eric Blake |
Subject: |
Re: m4sh bug (AS_VAR_IF) |
Date: |
Mon, 16 Aug 2010 14:38:12 -0600 |
User-agent: |
Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.7) Gecko/20100720 Fedora/3.1.1-1.fc13 Lightning/1.0b2pre Mnenhy/0.8.3 Thunderbird/3.1.1 |
On 08/16/2010 02:33 PM, Ralf Wildenhues wrote:
>> But the documentation makes no mention that this is required.
>
> Then the documentation needs fixing.
Agreed.
Something along the lines of stating that <value> must be a shell word,
and then giving an example with a string containing quotes and spacing
would be appropriate. Would you like to try your hand at it?
>
>> Furthermore,
>> it seems unnecessary to inflict such a requirement.
>
> Well, problem is, the user might just prefer single quotes, or some more
> complicated construct. With the current code, she can eat that cake
> too, but with fixed double-quoting that is ugly.
Indeed - from Autoconf's own testsuite of a supported use of AS_VAR_IF:
> tests/m4sh.at:1286:AS_VAR_IF([tmp], ['\a "weird" `value` with; $fun
'\''characters
It's much easier to require that the user provide a single shell word
than it is to make m4 learn how to parse all possible shell constructs.
--
Eric Blake address@hidden +1-801-349-2682
Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature