Robert Elz <[email protected]> wrote: > Your explanation has far too many implementation details as > assumptions. I can assure you that in the NetBSD sh calling > unset on most variables does not create anything in your state 2, > but rather in state 1. Why would one bother to remember anything > about variables that have been unset? > > There are a few exceptions in the implementation for various reasons, > but mostly it is like that - and absolutely always when the variable > was in "state 1" - unset of such a thing is simply a no-op.
You could do that this way, but this is not how traditional shells behave. Jörg -- EMail:[email protected] (home) Jörg Schilling D-13353 Berlin [email protected] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.org/private/ http://sf.net/projects/schilytools/files/'
