can not unset var, no such var

[Dedan]

I seem to running into a problem with special characters
: = ¶ and who knows what other charcters.
all other lines are working just fine

Code: Select all

    if {![info exists rp_ctr($text)]} {set rp_ctr($text) 0}
    incr rp_ctr($text) 1
    utimer $rp_seconds [list rp:dec $text]



proc rp:dec {text} {
  global rp_ctr
  incr rp_ctr($text) -1
  if {$rp_ctr($text) <= "0"} {unset rp_ctr($text)}
  return 0
}

<Zipp> [23:32] Tcl error in script for 'timer395':
<Zipp> [23:32] can't read "rp_ctr(Away Duration: 10hrs 29mins 57secs «Log: ON»)": no such element in array

any ideas?

thanks for the help

[strikelight]

I seem to running into a problem with special characters
: = ¶ and who knows what other charcters.
all other lines are working just fine

Code: Select all

    if {![info exists rp_ctr($text)]} {set rp_ctr($text) 0}
    incr rp_ctr($text) 1
    utimer $rp_seconds [list rp:dec $text]



proc rp:dec {text} {
  global rp_ctr
  incr rp_ctr($text) -1
  if {$rp_ctr($text) <= "0"} {unset rp_ctr($text)}
  return 0
}

<Zipp> [23:32] Tcl error in script for 'timer395':
<Zipp> [23:32] can't read "rp_ctr(Away Duration: 10hrs 29mins 57secs «Log: ON»)": no such element in array

any ideas?

thanks for the help

The problem is not with the chars, it is with repeat calls to rp:dec via the utimer with the same text. Perhaps you should add a check to see if you already have a utimer call for the text in question?

[Dedan]

this is happening even when the text is posted
1 time , other text works fine, i do see what you
are saying ... just tell me this,
how are you suppose to make a repeat
kicker without using a proc that unsets ALL vars?

[strikelight]

If all you are after is a repeat kicking script, my norepeats.tcl is in the archive here, which you can take a look at.

[Dedan]

this is part of a 300 line script, this is the last bug.
I would like to find out why i am getting these
erors when the text is only posted 1 time,
and only when there are special charaters
in the text.

[strikelight]

this is part of a 300 line script, this is the last bug.
I would like to find out why i am getting these
erors when the text is only posted 1 time,
and only when there are special charaters
in the text.

Welp...
the error:

<Zipp> [23:32] Tcl error in script for 'timer395':
<Zipp> [23:32] can't read "rp_ctr(Away Duration: 10hrs 29mins 57secs «Log: ON»)": no such element in array

Is generated from your 'incr rp_ctrl($text) -1' call.... not the unset...

I would change your proc to:

Code: Select all

proc rp:dec {text} { 
  global rp_ctr
  if {[info exists rp_ctr($text)]} {
    incr rp_ctr($text) -1 
    if {$rp_ctr($text) <= "0"} {unset rp_ctr($text)}
  }
  return 0 
}

[Dedan]

like i said before:
i am getting these erors when the text is only posted 1 time,
and only when there are special charaters in the text.

[strikelight]

like i said before:
i am getting these erors when the text is only posted 1 time,
and only when there are special charaters in the text.

Then I SUGGEST you give a different example, because the example you DID give does NOT contain any special characters that would result in any error.

Also, when the error occurs, doing '.tcl set errorInfo' in the partyline would also be of some benefit.

[Dedan]

edited

[strikelight]

I still do not see a new example yet.... with the text that triggers the script, and with the generated error, and the output of '.tcl set errorInfo'....

are you sure you want help?

[Dedan]

it happens when un-special characters
are in the text like ":" . ">>" , or "=)" are in the text

[Dedan]

if i chage the "rp:dec" as you suggested
the error messages will stop, but the bug still remains.
and that is, the var is NOT being set when
those characters are present in the text.

any character that is not a-Z 0-9 seems to
stop the script from setting the var

[strikelight]

if i chage the "rp:dec" as you suggested
the error messages will stop, but the bug still remains.
and that is, the var is NOT being set when
those characters are present in the text.

any character that is not a-Z 0-9 seems to
stop the script from setting the var

I can tell you that is not the case... as you should see from your own code... the error was generated from the timer call... your variable IS being set, as your code:

Code: Select all

    if {![info exists rp_ctr($text)]} {set rp_ctr($text) 0} 
    incr rp_ctr($text) 1 
    utimer $rp_seconds [list rp:dec $text] 

did NOT generate any error for you. If it was NOT being set, your "incr" statement would be error'ing on you.

[Dedan]

this script is running now in a room with
100's of lines of text being read by the eggdrop.
there are NO error messages unless there are
characters as i described.
the error messages happen when the text is posted 1 time.

there is no other common denominator.

[strikelight]

this script is running now in a room with
100's of lines of text being read by the eggdrop.
there are NO error messages unless there are
characters as i described.
the error messages happen when the text is posted 1 time.

there is no other common denominator.

and yet we still have not seen the output of '.tcl set errorInfo' when an error occurs................. .......... .............. ..............