egghelp/eggheads community

(re)loading single tcl files

2005-02-11T14:12:10-04:00

Haha, rehash... I could do this myself, but in case of debugging I have to reload my script often 10 times a row and always waiting 10sec till bot it rehashed is simply boring. So users uplevel solution is the best. Please only post, if you know a better solution than "source" .
for security... if someone hacks my dcc password, there is no worry about loading an extra script over dcc, since he cannot upload to /script without a trojaner on my machine . there you be no way to load from another path, because "script/*.tcl" is predefined, is there? I havent tested, if a containing [] would be executed, but I think it wouldnt, would it? but... even it would... when he has +n on partyline with my account he already has access to .tcl anyway... its useless to think about it .

Statistics: Posted by De Kus — Fri Feb 11, 2005 2:12 pm

(re)loading single tcl files

2005-02-11T12:29:11-04:00

As for the 'uplevel' thingy, for me lets stay we'll stick to the simple method at the moment.

what method is that?

Statistics: Posted by user — Fri Feb 11, 2005 12:29 pm

(re)loading single tcl files

2005-02-11T12:21:42-04:00

Sometimes the bot laggs on the shell and there can be various problems so using a small delayed utimer was my idea.

As for the 'uplevel' thingy, for me lets stay we'll stick to the simple method at the moment.

Statistics: Posted by awyeah — Fri Feb 11, 2005 12:21 pm

(re)loading single tcl files

2005-02-11T11:07:41-04:00

bla bla bla
utimer 2 rehash

'open file a' would make sure you're at the end...but adding a new 'source filename' every time you want to REload a script is not a good idea and detecting if the file is already added to the conf can be hard as it could be sourced in many ways. And why wait 2 seconds to rehash? Just rehash after you've closed the file.

hmm, ah thats how its meant to be used. ic, thx. this way the global var prob should be solved.

A even better method would be to replace "uplevel #0" with "*dcc:tcl " - that way it will also honor your must-be-owner setting.

Statistics: Posted by user — Fri Feb 11, 2005 11:07 am

(re)loading single tcl files

2005-02-11T09:20:53-04:00

I would suggest another thing by opening the .conf file going to the end and writing:

source scripts/$text.tcl

You will have to search for the last line in this case and then in the next "/n" empty line write down so that it loads. In this will always make it stay there untill you remove it.

Then make your proc execute a rehash:

utimer 2 rehash

Statistics: Posted by awyeah — Fri Feb 11, 2005 9:20 am

Re: (re)loading single tcl files

2005-02-11T05:22:16-04:00

Things that are overwritten in the interpreter cease to exist

Statistics: Posted by user — Fri Feb 11, 2005 5:22 am

Re: (re)loading single tcl files

2005-02-10T21:28:49-04:00

uplevel #0

hmm, ah thats how its meant to be used. ic, thx. this way the global var prob should be solved.
does someone know if the code will be double in memory, or will the procs be replaced not only in function but also in memory?

Statistics: Posted by De Kus — Thu Feb 10, 2005 9:28 pm

Re: (re)loading single tcl files

2005-02-10T19:34:27-04:00

uplevel #0

Statistics: Posted by user — Thu Feb 10, 2005 7:34 pm

(re)loading single tcl files

2005-02-10T19:00:51-04:00

Beware, if you have any faith, dont read the script. This script is very very old... but it worked almost perfect all the time .

Code:

########## .loactcl#bind dcc n loadtcl loadtclproc loadtcl {hand idx args} {  source scripts/$args.tcl  return 1}

I know, this is really really ugly. I dont even know, if I load the memory till ultimo, but however it loads the procs and overwrites the old one. The only real flaw is, that variables used outside of a proc are not considered as global. I thought about using utimer to execute "source" globally, but I wonder if there isnt a more suitable command for that purpose? I couldnt find something in the tcl command list myself.

Statistics: Posted by De Kus — Thu Feb 10, 2005 7:00 pm