[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: sh portability questions
From: |
Andreas Schwab |
Subject: |
Re: sh portability questions |
Date: |
Wed, 28 Sep 2005 00:24:51 +0200 |
User-agent: |
Gnus/5.110003 (No Gnus v0.3) Emacs/22.0.50 (gnu/linux) |
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.
Andreas.
--
Andreas Schwab, SuSE Labs, address@hidden
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
- sh portability questions, Akim Demaille, 2005/09/27
- Re: sh portability questions, Paul Eggert, 2005/09/27
- Re: sh portability questions,
Andreas Schwab <=
- 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
- Re: sh portability questions, Keith Marshall, 2005/09/29