#496 Correct upvar and uplevel error message

[Anonymous]

upvar and uplevel give misleading error message when level argument is defaulted to 1 but doesn't exist. For example:
% upvar x y
bad level "x"
% uplevel puts Hello
bad level "puts"

The patch alters TclGetFrame routine to remedy that, so the message is:

bad level "1"

{ DXDragon@yandex.ru }

[Nobody/Anonymous]

The mighty one-line patch

[miguel sofer]

Logged In: YES
user_id=148712
Originator: NO

The error message would be misleading for
upvar x a b