When I create symbolic links (on solaris and linux,
tcl8.4.4) using [file link -symbolic ...] command, the
created link file always points to an absolute path
even when a relative path is specified. This is causing
problems when the directory is moved around and the
links have to be deleted and re-created. Is this the
correct behavior (dictated by cross-platform support)?
It would be nice if the [file link] command behaved
like the unix 'ln' utility in this respect so that I
don't have to invoke [exec ln -s ...] for creating
I don't see that this is specifically mentioned
anywhere in the docs
of the implementation. It seems a byproduct of the
request returning a fully qualified path. I'm not sure
is a bug, so I've cc'ed the implementor, Vince Darley.