#1654 update idletask

obsolete: 8.3.3
closed-invalid
5
2001-10-16
2001-10-16
Anonymous
No

I have found a strange aspect of tcl 8.3.3 "update"
command on Windows.
See the example below:

% update
% update a
bad option "a": must be idletasks
% update i
% update id
% update idl
% update idle
% update idletask
% update idletasks
% update idletaskss
bad option "idletaskss": must be idletasks

Anyone knows why "update i" does not throw an error
and what update between
"update" and "update idletasks" is executed ?

Discussion

    • status: open --> closed-invalid
     
  • Logged In: YES
    user_id=79902

    This (allowing unambiguous prefixes instead of requiring the
    subcommand to be written out in full) is the defined
    behaviour of Tcl w.r.t. subcommands, and is implemented by
    Tcl_GetIndexFromObj which you should refer to for more
    information.

    NB: Robust scripts do not use prefixes, but for interactive
    use they are a god-send.