egghelp/eggheads community

premature end of expression?

2003-01-15T07:07:20-04:00

I have also noticed that the user is not removed from the list and fixed that. Seems that someone forgot to add them.

So, how to fix the bold thinghie then?

Statistics: Posted by caesar — Wed Jan 15, 2003 7:07 am

premature end of expression?

2003-01-15T06:47:11-04:00

Oups.. You are right, as usualy.. :]

Statistics: Posted by caesar — Wed Jan 15, 2003 6:47 am

premature end of expression?

2003-01-15T06:42:23-04:00

No - it is the way Tcl handles lists.

Lists are handled as is, without any normal subtitution.

IE.

Code:

set list {hello $nick, \002how\002 are you [time]}set string "hello $nick, \002how\002 are you [time]"

In the above, the $string varialbe will be correct, with both the $nick, the codes correctly translated and the command "time" replaced with whatever it returns.

Lists however, are considered lieraly. IE, $ nick is considered a word, and not a variable, and should be placed as is. The same applies to the codes.

The "subst" command can be used to get around this, and will make the substitution on demand, rather than the time the variable is set.

Statistics: Posted by ppslim — Wed Jan 15, 2003 6:42 am

premature end of expression?

2003-01-15T06:39:31-04:00

When the welcome msg is like this: "You are number \002!number!\002 in line." It dosen't return the value of !number! Ex: You are number \002!number!\002 in line.

When the welcome msg is like this: "You are number \002 !number! \002 in line." It dosen't get number with bold and is the same till now. Ex: "You are number \0021 \002 in line."

Statistics: Posted by caesar — Wed Jan 15, 2003 6:39 am

premature end of expression?

2003-01-15T06:34:11-04:00

As I can see the next:moretools:replace proc is 'eating' them..

Statistics: Posted by caesar — Wed Jan 15, 2003 6:34 am

premature end of expression?

2003-01-15T06:32:50-04:00

Find the proc next:moretools:replace

At the end of it, you have "return $text"

Change this to

return [subst $text]

Statistics: Posted by ppslim — Wed Jan 15, 2003 6:32 am

premature end of expression?

2003-01-15T06:25:04-04:00

Nope. Same thing happens. "You are number \002 1 \002 in line."

Statistics: Posted by caesar — Wed Jan 15, 2003 6:25 am

premature end of expression?

2003-01-15T06:20:55-04:00

Change the line in the next(welcome) setting from

You are number \002!number!\002 in line. NO colours

You are number\002 !number! \002in line. NO colours

Statistics: Posted by ppslim — Wed Jan 15, 2003 6:20 am

premature end of expression?

2003-01-15T06:17:20-04:00

Seems that we have fixed the problem. Thanks. How to fix this thing: "You are number \0021\002 in line". The number 1 should be with bold and is not. Where is the problem?

Statistics: Posted by caesar — Wed Jan 15, 2003 6:17 am

premature end of expression?

2003-01-15T05:56:33-04:00

OK - From your posting, it has become self evident what the issue is. It seems the list is being malformed. Those values should be on one line, rather than 2.

I have found the issue from this.

When the first person is added to the list, the script will select between using the "set" or "lappend" commands, based on if the list for that channel exists.

The problem is, it uses "set" if the list doesn't exist.

To fix this, we can hardcode it to use "lappend", which creates the list if need be.

Find and locate the "next:cmds" proc. The first switch method is add_list. Within this segment, locate the 2 line

Code:

set temp(cmd) [expr {![info exists next(:list:$channel)]?"set":"lappend"}]$temp(cmd) next(:list:$channel) [list $nick [clock seconds]]

Change them to the following

Code:

lappend next(:list:$channel) [list $nick [clock seconds]]

AKA, delete the first line (can be done with CTRL+K while on the line in pico), and change the first part of the second command.

Statistics: Posted by ppslim — Wed Jan 15, 2003 5:56 am

premature end of expression?

2003-01-15T05:43:38-04:00

I've used this code:

bind pub n .users list:users

proc list:users {nick host hand chan arg} {
global next
set temp(list) [next:cmds get_list $chan]
foreach element $temp(list) {
putlog "Element on list: $element"
}
}

and here is what I got:
[11:40] Element on list: moo
[11:40] Element on list: 1042623583

Statistics: Posted by caesar — Wed Jan 15, 2003 5:43 am

premature end of expression?

2003-01-14T12:25:03-04:00

Well I didn't had a problem with the duration till I've upgraded my eggdrop to 1.6.13, so I think there is not an problem with the list. Anyway I'll test if the list is well made as should be done.

Statistics: Posted by caesar — Tue Jan 14, 2003 12:25 pm

premature end of expression?

2003-01-14T12:01:13-04:00

Oh and..

A1: yes and on other commands that use "duration".

A2: It seems to work fine, I'm getting the error only when I use one of the commands that use "duration".

Caesar, there are 2 instances in your script where the "temp(duration)" is computed just after you have created the list by using "set temp(list) [next:cmds get_list $chan]".

By adding putlog statements can you inspect that this list is a proper list? Like as follows:

Code:

set temp(list) [next:cmds get_list $chan]foreach element $temp(list) {   putlog "Element on list: $element"}

Statistics: Posted by egghead — Tue Jan 14, 2003 12:01 pm

premature end of expression?

2003-01-14T11:14:33-04:00

Oh and..

A1: yes and on other commands that use "duration".

A2: It seems to work fine, I'm getting the error only when I use one of the commands that use "duration". Normal users and helpers join the channel and the normal ones recive the notice (as shoud do) and the helpers recive an voice (again like should do).

Commands that use the "duration": .next and .list

Statistics: Posted by caesar — Tue Jan 14, 2003 11:14 am

premature end of expression?

2003-01-14T11:13:29-04:00

I havn't sugested that you get the error when they join.

The error occurs when a list is requested.

I need to know, where the data (or lack of) is coming from, that cuases it.

Information is changed, when a user joins, quits, parts or changes nicknames.

It is at these times the data becomes currept, but which one.

As such, you need to force it to send a list, each time of of these events occurs, and state after whcih one it occurs.

Statistics: Posted by ppslim — Tue Jan 14, 2003 11:13 am