autoconf-patches
[Top][All Lists]
Advanced

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

Why does AS_UNSET export the variable?


From: Stepan Kasal
Subject: Why does AS_UNSET export the variable?
Date: Wed, 22 Aug 2007 14:06:05 +0200
User-agent: Mutt/1.4.2.3i

Hello,
  I noticed that AS_UNSET uses export at the end.  So we have

        $as_unset ac_configure_args0 ||
          test "${ac_configure_args0+set}" != set ||
          { ac_configure_args0=; export ac_configure_args0; }

I do not think the export makes sense.  When unset is not available
and the variable is set, it is enough to set the neutralizing value.

If the variable was not exported, then child processes will not get
it, which is as good as if it was unset.  If the variable was
exported, the export is redundant.

What about the following patch?

Have a nice day,
        Stepan

Attachment: autoconf-20080822-as-unset.patch
Description: Text document


reply via email to

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