[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: updated win32 macro
From: |
Lars J. Aas |
Subject: |
Re: updated win32 macro |
Date: |
Thu, 15 Mar 2001 14:12:56 +0100 |
User-agent: |
Mutt/1.2.5i |
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, (continued)
- Re: updated win32 macro, Robert Collins, 2001/03/15
- Re: updated win32 macro, Christopher Faylor, 2001/03/15
- Re: updated win32 macro, Robert Collins, 2001/03/15
- Re: updated win32 macro, Akim Demaille, 2001/03/19
- Re: updated win32 macro, Robert Collins, 2001/03/19
- Re: updated win32 macro, Akim Demaille, 2001/03/19
- win32 v4, Robert Collins, 2001/03/15
- Re: updated win32 macro, Robert Collins, 2001/03/15
- Re: updated win32 macro, Christopher Faylor, 2001/03/15
- Re: updated win32 macro, Lars J. Aas, 2001/03/15
- Re: updated win32 macro,
Lars J. Aas <=
Re: updated win32 macro, Akim Demaille, 2001/03/15
Re: updated win32 macro, edward, 2001/03/15
Re: updated win32 macro, Robert Collins, 2001/03/15
Re: updated win32 macro, edward, 2001/03/15