egghelp/eggheads community

Weird behavior of FOREACH command

2008-02-04T13:12:42-04:00

and stop using list commands on strings.
split the sting into a var and then
use the foreach ....

global botnick
if the botnick var was not called then it will produce
an error and stop the loop

Statistics: Posted by Dedan — Mon Feb 04, 2008 1:12 pm

Weird behavior of FOREACH command

2007-12-09T17:57:56-04:00

@nml375: I know the way I use is not really good, but it works.

@z_one: the second example I gave is working because it use the logical way to transform a string into a list.

Statistics: Posted by CrazyCat — Sun Dec 09, 2007 5:57 pm

Weird behavior of FOREACH command

2007-12-09T16:13:08-04:00

Yeah, sorry about that botnick thing ... I forgot to copy it here as I was typing the code manually.

So basically, nml375, if I use the list-command I can use any of the following ?

Code:

set thechanlist [list #chanA #chanB #chanC]

Code:

set thechanlist [list "#chanA" "#chanB" "#chanC"]

Code:

set thechanlist [list {#chanA} {#chanB} {#chanC}]

I think Crazycat's second example should work too because the split-command would turn the string "#chanA #chanB #chanC" into a list right ?

Thank you both for the replies.

Statistics: Posted by z_one — Sun Dec 09, 2007 4:13 pm

Weird behavior of FOREACH command

2007-12-09T13:07:41-04:00

@CrazyCat:

Code:

{"#chanA" "#chanB" "#chanC"}

This is just as much a string as the code used by z_one..
To make proper list, use the list-command (or split).
Ie:

Code:

set thechanlist [list #chanA "#chanB" {#chanC}]

@z_one:
If you use the global-command to link a localspace variable to the globalspace one, you don't need to use full namespace paths for that variable. In the same way, if you use full namespace path, there is no reason to use "global". Nothing wrong with doing both I guess, except that you might forget that the localspace variable is linked to the globalspace in larger scripts.

I do however notice that you try to access the globalspace variable botnick as a localspace variable without using "global". This should cause an error, and prematurely abort the proc with an error condition.

Statistics: Posted by nml375 — Sun Dec 09, 2007 1:07 pm

Weird behavior of FOREACH command

2007-12-09T07:10:59-04:00

You set a string, not a list or array.
You can use:

Code:

# list of channelsset thechanlist {"#chanA" "#chanB" "#chanC"}proc whereisthebot {} {  foreach chan $::thechanlist {    if {[botonchan $chan]} {      putlog "$botnick is on $chan"    }  }}

Or if you want to keep your initial setting:

Code:

# list of channelsset thechanlist "#chanA #chanB #chanC"proc whereisthebot {} {  foreach chan [split $::thechanlist " "] {    if {[botonchan $chan]} {      putlog "$botnick is on $chan"    }  }}

Statistics: Posted by CrazyCat — Sun Dec 09, 2007 7:10 am

Weird behavior of FOREACH command

2007-12-09T02:41:01-04:00

Code:

# list of channels set thechanlist "#chanA #chanB #chanC" proc whereisthebot {} {   global thechanlist  foreach chan $::thechanlist {     if {[botonchan $chan]} {       putlog "$botnick is on $chan"     }   } }

Then in the bot .conf file I have added ChanA, ChanB and ChanC in this exact order. The script works fine.

Now, whenever I set the variable thechanlist to "#chanC #chanA #chanB" for example ... then the foreach loop just goes over ChanC and doesn't go over the two other chans.

I don't get it. What does the variable thechanlist have to do with the bot's .conf file ?

Statistics: Posted by z_one — Sun Dec 09, 2007 2:41 am