Re: Silent overriding of the command?

From: Cameron Laird (claird_at_lairds.com)
Date: 11/13/03 

Date: Thu, 13 Nov 2003 14:44:50 -0000

In article <bp02i4$1jmcn1$1@ID-148741.news.uni-berlin.de>,
Ulrich Schoebel <ulrich.schoebel@tclers.tk> wrote:
>Hi Victor,
>
>this is _not_ a Tcl 8.4 feature, it has always been so.
>You only have to rename Tcl commands, if you want to use
>the original command later on. So there is no bug to file.
                        .
                        .
                        .
True.

I know Victor's experienced with Tcl, and I wonder if there's some
deeper story afoot here. I've certainly heard others mention re-
lated needs--that their design requires, for example, a way to
"lock in" specific commands, so that they canNOT be overwritten.
I've never needed such in my own work ...

I suspect if I spent time, I could find "prior art" for a modified
[proc] that refuses to overwrite existing commands. It should only
take a dozen lines, in any case.

ALSO, note that recent (I'll not make the time now to research its
introduction) Tcl-s provide [trace] capabilities triggered on com-
mand modifications. That's the contemporary way to implement
solutions in this area. 

-- 
Cameron Laird <claird@phaseit.net>
Business:  http://www.Phaseit.net