On Thu, Mar 15, 2001 at 01:18:37PM +0100, Lars J. Aas wrote: : I agree, but I'd rather have the implementation/optimization details hidden : in some autoconf-provided variables like $as_true and $as_false - it would : be less obfuscating. Then you could set $as_true to ":" and perhaps $as_false : to "(exit 1)" if "false" for some reason does not work on a system. Just "(exit 1)" didn't work, but this does: as_true=":" as_false="eval (exit 1)" Don't know what's more optimal of that and fork + exec /bin/false. Could probably go the way of fork + eval... Lars J -- Innovation is one percent inspiration and ninetynine percent perspiration, and in my case; twice that... -- Norville Barnes, `The Hudsucker Proxy'
- Re: updated win32 macro edward
- Re: updated win32 macro Akim Demaille
- Re: updated win32 macro Robert Collins
- Re: updated win32 macro Akim Demaille
- Re: updated win32 macro Robert Collins
- Re: updated win32 macro Robert Collins
- Re: updated win32 macro Robert Collins
- Re: updated win32 macro Akim Demaille
- Re: updated win32 macro Akim Demaille
- Re: updated win32 macro Lars J. Aas
- Re: updated win32 macro Lars J. Aas
- Re: updated win32 macro Robert Collins
- Re: updated win32 macro Akim Demaille
- Re: updated win32 macro Robert Collins
- Re: updated win32 macro Akim Demaille
- Re: updated win32 macro Robert Collins
- Re: updated win32 macro edward
- Re: updated win32 macro Akim Demaille
- Re: updated win32 macro Earnie Boyd
- Re: updated win32 macro Robert Collins
- Re: updated win32 macro Earnie Boyd
