Re: Windows env-Bug?
- From: Helmut Giese <hgiese@xxxxxxxxxxxxx>
- Date: Sat, 21 Jul 2007 20:33:55 +0200
On Sat, 21 Jul 2007 13:31:04 -0000, Torsten Edler
<Torsten.Edler@xxxxxxxxxxxxxx> wrote:
This not a tcl feature - this is a windows feature. Try this at the
windows prompt
set XX=AA
is setting the variable to value AA. can be checked by using
set
and unsetting the variable can be done by
set XX=
which is setting the variable to empty string - and in windows this
means deleting the variable! Again another check will confirm that the
variable XX is gone. Same can be done in TCL via the env array and
using parray.
While this is true, the fact that
set env(Test) ""
info exists env(Test)
returns '1' is certainly unfortunate.
It seems that
set env(Test) ""
set Tcl's copy of 'env' to "" - which is perfectly legal for a Tcl
array, thus causing [info exists] to return '1' - but when trying to
retrieve this supposedly existing element, Tcl seems to go out asking
Windows for the value - and for Windows it doesn't exist any more.
Probably it would be quite messy to fix this.
Just my 0.02
Helmut Giese
.
- Follow-Ups:
- Re: Windows env-Bug?
- From: Torsten Edler
- Re: Windows env-Bug?
- References:
- Windows env-Bug?
- From: Gerhard Reithofer
- Re: Windows env-Bug?
- From: Torsten Edler
- Windows env-Bug?
- Prev by Date: selecting multiple directories with tk
- Next by Date: Re: Help: Auto Upgrade Data from FTP
- Previous by thread: Re: Windows env-Bug?
- Next by thread: Re: Windows env-Bug?
- Index(es):
Relevant Pages
|