Re: unset variables, was Re: please correct my ugly hack

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

 



On Thu, 2 Jun 2005, Paul Eggert wrote:

> Dan Manthey <dan_manthey@xxxxxxxxxxx> writes:
>
> > For that matter, I know you can set bash to error out on $var for an
> > unset var
>
> Let's not do that, please.  Let's stick to traditional behavior
> blessed by POSIX.  If Bash's behavior is inherited I suppose we should
> turn it off.
>

Oh, I didn't mean to advocate this at all.  I set Bash to have this
behavior when it's my interactive shell, and I somehow managed to run
configure with it, causing configure to fail.  I think had to go through
some rigamarole to do this, so I wouldn't worry about it, but it might be
appropriate to explicitly disable the feature during the cleaning at start
up.  *Shrug.*  Clearly, this isn't a big issue, though.

-Dan


_______________________________________________
Autoconf mailing list
Autoconf@xxxxxxx
http://lists.gnu.org/mailman/listinfo/autoconf

[Index of Archives]     [GCC Help]     [Kernel Discussion]     [RPM Discussion]     [Red Hat Development]     [Yosemite News]     [Linux USB]     [Samba]

  Powered by Linux