[Tcl-bugs] [ tcl-Bugs-1274918 ] doc: upvar and qualified varNames

[SourceForge.net <no...@so...>]

Bugs item #1274918, was opened at 2005-08-27 22:36
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=110894&aid=1274918&group_id=10894

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: 07. Variables
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: miguel sofer (msofer)
Assigned to: miguel sofer (msofer)
Summary: doc: upvar and qualified varNames

Initial Comment:
This supersedes Bug #959831.

There are two (related, important) issues that the
[upvar] docs do not describe: what it does when called
outside a proc body, and how it handles qualified
variable names.

The behaviour outside of proc bodies just needs
documenting: 
   upvar ?level? otherVar myVar ?otherVar myVar ...?
will create a variable named myVar in the current
namespace (assuming for now that myVar is not
qualified) linked to the variable otherVar as resolved
in the corresponding stack frame. This is the same
behaviour as documented in upvar.c, just replacing
"current procedure" by "current context". The fact that
this variable can never be unset until the namespace is
deleted deserves mention - and maybe a fix too?

The behaviour when otherVar is qualified is completely
unspecified in the manual page. This may not be a
problem, the behaviour is without surprises: the
variable that is linked to is otherVar as resolved in
the corresponding stack frame.

The behaviour when myVar is qualified is also
unspecified in the manual page, and is currently buggy
(Bug #1274916).

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=110894&aid=1274918&group_id=10894