[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: sh portability questions
From: |
Paul Eggert |
Subject: |
Re: sh portability questions |
Date: |
Tue, 27 Sep 2005 15:36:06 -0700 |
User-agent: |
Gnus/5.1007 (Gnus v5.10.7) Emacs/21.4 (gnu/linux) |
Andreas Schwab <address@hidden> writes:
> Paul Eggert <address@hidden> 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.
- sh portability questions, Akim Demaille, 2005/09/27
- Re: sh portability questions, Paul Eggert, 2005/09/27
- Re: sh portability questions, Akim Demaille, 2005/09/28
- Re: sh portability questions, Paul Eggert, 2005/09/28
- Re: sh portability questions, Ralf Wildenhues, 2005/09/28
- Re: sh portability questions, Andreas Schwab, 2005/09/28
- Re: sh portability questions, Akim Demaille, 2005/09/28
- Re: sh portability questions, Ralf Wildenhues, 2005/09/28