Chanpro2.2.tcl Regexp Error

blood_x · Post by **blood_x** » Sun May 09, 2004 1:12 pm

Hi there,

I'm using no.spam1.7.2.tcl for my eggdrop. But sometime msg as below appears;

Tcl error [check_pubm]: couldn't compile regular expression pattern: brackets [] not balanced

How to fix it up?

Thanks.

p/s: No.spam1.7.2 written by ppslim can be found here.

ppslim · Post by **ppslim** » Mon May 10, 2004 5:29 am

It's not my script causing that.

My scripts consists of only two regular expressions, both of which are all 100% valid.

Beyond that, there is no procedure called check_pubm. Which sugests another script you have loaded.

blood_x · Post by **blood_x** » Mon May 10, 2004 9:25 am

Opss, I'm so sorry for it, ppslim. Argh, mistake done! WooPs, I've changed the topic k

. After review one by one TCL scripts that I have loaded, I found that "Chanpro2.2.tcl" make the regexp error as stated before.

Here is check_pubm proc;

proc check_pubm {nick host hand chan text} {

#load some global variables
global chanpro botnick

#set some variables
set botnicky [string tolower $botnick]
set chan [string tolower $chan]
set enabled [lsearch -exact $chanpro(chans) $chan]
set host [string tolower $host]

#check if the chan enabled, else return..
if {!$chanpro(all) && $enabled == -1} {return 0}

#check if the bot is OPed, else return..
if {![botisop $chan]} {return 0}

#check if the bot is actually typing the word himself, if so - return..
if {[string tolower $nick] == $botnicky} {return 0}

#check if other bot is actually typing the word <- Added to fix bugs
if {[matchattr $hand +b]} {return 0}

#check the text for colors, bold, underline and CAPS
if {[string match *\003* $text]} {check_color $nick $host $hand $chan $text} \
elseif {[string match *\002* $text]} {check_bold $nick $host $hand $chan $text} \
elseif {[string match *\037* $text]} {check_underline $nick $host $hand $chan $text} \
else {check_caps $nick $host $hand $chan $text}

} ;#end proc

And how to fix it up?

dollar · Post by **dollar** » Mon May 10, 2004 11:00 am

Pasting the regexp would help...

blood_x · Post by **blood_x** » Mon May 10, 2004 2:08 pm

I found one match for "regexp" as below;

6 {
if {[regexp ^(\[0-9.\])+$ [set parsed [lindex [split $host @] 1]]]} {
set parsed *!*[lindex [split $host @] 0]@[join [lrange [split $parsed .] 0 1] .].*
} elseif {[string match -nocase *.users.undernet.org* $host]} {
set parsed *!*@[lindex [split $host @] 1]
} else {
set first [split $host @]
set second [split [lindex $first 1] .]
set parsed *!*[lindex $first 0]@*.[lindex $second end-1].[lindex $second end]
}
}

Alchera · Post by **Alchera** » Mon May 10, 2004 4:27 pm

#check if the bot is actually typing the word himself, if so - return..
if {[string tolower $nick] == $botnicky} {return 0}

Noticed a typo in check_pubm, "$botnicky". Change to "$botnick".

(A little off the track)

blood_x · Post by **blood_x** » Mon May 10, 2004 4:57 pm

Opss, but it is some variables (as in the script)

set botnicky [string tolower $botnick]

Still typo faulty?

Alchera · Post by **Alchera** » Mon May 10, 2004 5:18 pm

Woops? lol

blood_x · Post by **blood_x** » Tue May 11, 2004 6:30 pm

WooOOops! Still no answer.. on how to fixed it up

Alchera · Post by **Alchera** » Sun May 16, 2004 3:12 pm

Hi,

I'm no genius with regexp, but try this:

if {[regexp {^(\[0-9.\])+$} [set parsed [lindex [split $host @] 1]]]}

Hope that fixes it.