[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

unset variables, was Re: please correct my ugly hack

From: Dan Manthey
Subject: unset variables, was Re: please correct my ugly hack
Date: Thu, 2 Jun 2005 16:01:17 -0400

On Thu, 2 Jun 2005, Stepan Kasal wrote:

> it uses    test "x$VAR" = x
> Thus the manual should use the term "is nonempty", not "is set".
> (One of the reasons for this behaviour is that unset is not portable.)

It's documented that the builtin `unset' is non-portable, but what about
the use of unset variables vs. empty variables?  Is this distinction
always meaningful?  (Some of the caveats about MS DOS suggest not?)  Also,
I know that ${var:-default} is not portable.  Is ${var-default}?  For that
matter, I know you can set bash to error out on $var for an unset var,
which would require ${var-}.  I'm ignorant:  is this behavior turned off
by AC_INIT (or whatever)?


Attachment: autoconf-20041027-check_prog.patch
Description: Text document


Autoconf mailing list


reply via email to

[Prev in Thread] Current Thread [Next in Thread]