> > Well, if you really wanted a workaround, you could always unset the
> > variable in the after command :)
>
> 'unset' is there to simulate a local variable or temporary variable. It
> can't be moved into the after command. You don't need to 'unset' if you
> just put the whole thing inside a proc.
I was kidding, see that :) at the end.
> Well, there are things like file handles, which are locked down.
>
> set x [file open foo]
> fileevent $x readable "read $x"
> unset x
That is not the same thing. A file handle must be closed with the close
command. The close command is like a destructor for an object. Java
objects have no destructor, so there is no functional mapping.
A file handle in Tcl is just a hash table mapping from the
string name to the file descriptor.
"file0" -> int or whatever
Mo DeJong
Red Hat Inc
----------------------------------------------------------------
The TclJava mailing list is sponsored by Scriptics Corporation.
To subscribe: send mail to [EMAIL PROTECTED]
with the word SUBSCRIBE as the subject.
To unsubscribe: send mail to [EMAIL PROTECTED]
with the word UNSUBSCRIBE as the subject.
To send to the list, send email to '[EMAIL PROTECTED]'.
An archive is available at http://www.mail-archive.com/tcljava@scriptics.com
