egghelp.org community

[dj-zath]

Recently, I upgraded from a hosted box running FreeBSD.. to a CoLocation box running Linux.

I was running an older version of eggdrop on the bsd box, but opted to run the latest TCL and eggdrop on this new box..

everything compiled and installed without any problems.. untill...

I went to load a custom script I wrote to manage my radio station interface..

BZZZZT! the script COMPLETELY FAILS!

okay, I thought, I figured I'd probably have to change things and would begin rewriting the script from scratch..

then I discovered WHY the script failed... and I'd like to know if this was intentional or whatnot... and how to FIX it...


I didn't get very far- in fact, right on the first piece of code/procs..

I have discovered the following:

1 timers will NOT run, period.
2 a proc will NOT load another proc... (list does NOTHING)
3 can't have a 'if{}' statement outside a proc (such as in the eggdrop.conf file)

an 'if' statement will run inside a proc, but ONLY if a GLOBAL varable is set; "local" varables don't work in 'if' statements- in or out of procs

so, the following piece of code:

[nml375]

Could you provide some additional information, such as version of eggdrop, version of tcl, the full source of your custom script, any generated/logged errors?

1. Odd, do you get any errors logged or such?
   
   
2. The list command does not call another proc, it simply generates a tcl-list. It is used with timers to prevent code injection and remote exploits, such as command substitutions ([command]) and variable evaluation.
   This would rather be a side-effect of your first problem.
   
   
3. This is very odd. Tcl should not make any difference to what commands are available simply by changing the command execution context. Did you get any errors when trying this?
   
   
4. Variable context must be considered. A globalspace variable is not implicitly made available to the environment of a proc, but must explicitly be made available using the upvar or global commands. A local variable within a proc will only persist through the execution of the proc, and is wiped once the proc ends. Any variable already created within the current instance of the proc should be usable with if, aswell as any other command, without having to link it to a globalspace variable.

Personally, I can not see any reason for the posted code not working (I am assuming there is a proc named Action aswell somewhere in your script). I also assume the pasted code is executed at global context, and StartLoop has not been set prior running this code.
_________________
NML_375, idling at #eggdrop@IrcNET

[dj-zath]

hi and thanks for your prompt reply!

a couple things to explain reguarding your inquiry.

1.. the "code" I provided above was just an example- it assumes a proc named "Action" exists.

2.. the actual code I have for the radio interface is rather lengthy.. and I'd rather not post it since it contains sensitive information (of course, I could "bleep out" that info.. but I might miss something... and that will bite me in the ass later on )

3. I think the code itself would work once the "base" parts are figured out..

I have began to use "debug mode".. and now I see the error messages ( call it a brain fart or what!) The error messages still don't make sense, however, but at least I see whats happening...

the args/flags for called procs are being dropped and/or ignored

note the following example:

heres a example piece of code I put in:

[speechles]

Your problem is painfully obvious and the error given to you clearly spells it out.

[nml375]

As speechles pointed out, you must always make sure function calls have the right number of arguments. Different bindings will call the associated function with a set of arguments depending on the type of the binding, and hence your proc must match that. Also, keep in mind that there is no automatic variable injection or such when calling a function from another function..

Since your problems started when you upgraded your eggdrop, I would guess it is related to one of a few binding types that has been altered in a non-backwards compatible manner. These are notc, part, and mode (pre 1.3.18 ); see the tcl-commands.doc document for further information on compability with these commands, including portable code.
_________________
NML_375, idling at #eggdrop@IrcNET

[dj-zath]

DING!

okay okay! I get cha!

yeah, the old code didn't require sending the args/flags along with a run/list command... (though I DID include them in the "controlled" proc..)

since the writing of the previous post, I have "worked around" as many issues as I could... mainly sticking all the "timer-controlled" procs (updates) into a SINGLE proc and then binding that to "time" (the number of globals is SCARY!)

I still noticed that NO expressions or if/else works unless I set those particular varables as a global even if the if statment is still inside the SAME proc as the varable! setting the varable as a global works- even though that varable will NEVER be used outside the proc (isn't that a whaste of resources??) for this reason, I'm cirrently at 46 "global" varables and expect to climb to over 100! (I hope there isn't a LIMIT!)

because it was requested: and now I can access the web at this terminal)

heres the ACTUAL code, from the OLD Bot, reguarding the timers..

[dj-zath]

okay.. I think I got it working...

heres the NEW code..

[nml375]

A few thoughts comes into mind reading your last two posts.