Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com Date: Thu, 15 Mar 2001 13:18:37 +0100 From: "Lars J. Aas" To: Alexandre Oliva Cc: Robert Collins , cygwin-apps AT sources DOT redhat DOT com, autoconf AT gnu DOT org Subject: Re: updated win32 macro Message-ID: <20010315131837.A20123@sim.no> References: <035401c0ac91$3ba21fd0$0200a8c0 AT lifelesswks> <022001c0accf$29b724d0$0200a8c0 AT lifelesswks> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from oliva@lsd.ic.unicamp.br on Thu, Mar 15, 2001 at 02:51:08AM -0300 On Thu, Mar 15, 2001 at 02:51:08AM -0300, Alexandre Oliva wrote: : On Mar 14, 2001, "Robert Collins" wrote: : : > version 2.. returns true/false now. I've also updated te sample code : > to reflect this : : Better use `:' instead of `true'. I'm not sure `:' is more portable, : but at least it's a built-in in more shells than `true'. 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. Lars J