Re: sh portability questions

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

 



Andreas Schwab <schwab@xxxxxxx> writes:

> Paul Eggert <eggert@xxxxxxxxxxx> writes:
>
>> Assuming you don't need recursion, here's a thought.  Use "local", but
>> stick to the convention that all variable names are unique.  On
>> systems that don't support "local", define a function named "local"
>> that warns if any of its arguments is a variable whose value is set;
>
> That would also (spuriously) warn if you call a function with local
> variables a second time, unless you explicitly unset the local variables
> before returning.

Ouch.  You're right.

I guess the best we can do is define a function "local" that does nothing.


_______________________________________________
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