egghelp/eggheads community

constraining socket data

2004-07-12T03:01:22-04:00

then it didnt send the msg to the channel...

but I've solved the problem by making a separate proc for the msg to the channel, and triggering that after the setting of the variables - now it's not repeating

thanks for the help though!

Statistics: Posted by NewzUK — Mon Jul 12, 2004 3:01 am

constraining socket data

2004-07-09T17:03:39-04:00

Ooops what about after the else? (but still inside the main if part)

Statistics: Posted by stdragon — Fri Jul 09, 2004 5:03 pm

constraining socket data

2004-07-09T06:44:48-04:00

just tried it and still no luck...
this is what the problem looks like:
[22:40:16] [GE] GE 'CONFIDENT' OF 10%-15% EPS GROWTH FOR 2005
[22:40:47] [GE] GE REVISES FULL-YEAR EARNS RANGE TO $1.55-$1.60/SHR
[22:41:16] [GE] GE 'CONFIDENT' OF 10%-15% EPS GROWTH FOR 2005
[22:41:48] [GE] GE REVISES FULL-YEAR EARNS RANGE TO $1.55-$1.60/SHR
[22:42:16] [GE] GE 'CONFIDENT' OF 10%-15% EPS GROWTH FOR 2005
[22:42:46] [GE] GE REVISES FULL-YEAR EARNS RANGE TO $1.55-$1.60/SHR

top 2 headlines just repeat and dosn't stop at the first one, even with the check to see if it's old or not...
aghrrr

Statistics: Posted by NewzUK — Fri Jul 09, 2004 6:44 am

constraining socket data

2004-07-08T20:31:40-04:00

Try putting the return after this line:

putserv "PRIVMSG #channel :/0034,4 /0031,15 $rtr /00314,14 /003"

Statistics: Posted by stdragon — Thu Jul 08, 2004 8:31 pm

constraining socket data

2004-07-06T22:04:32-04:00

thanks strikelight - have put a return in at the end ( I think that's the right position?), and for the individual calls, it stops and just sends the top line. But the next time it runs, if that first story hasn't changed, instead of stopping, it gets the second oldest story. It's hard to explain...not sure how else I can demonstrate?

Statistics: Posted by NewzUK — Tue Jul 06, 2004 10:04 pm

constraining socket data

2004-06-30T20:00:31-04:00

Break from the loop and procedure by calling "return" where you want it to exit...

Statistics: Posted by strikelight — Wed Jun 30, 2004 8:00 pm

constraining socket data

2004-06-30T05:03:10-04:00

Hi - This relates sort of to a previous script I've sought help on - please excuse the long explaination!
I have a script to retrieve news headlines from a website - and with help from here, I've set up a check using variables so that the headlines don't repeat if there isn't a new one since the last check.
This works fine on the sites that only have one news headine on the page, however, when I try to use it on a page that has a list of headlines where there is no unique html code to identify only the newest top headline, the check system goes haywire.
It gets the top line, then on the next check, it sees that it is the same as before and instead of stopping, goes onto the next story down and sends that to the channel. On the next check it goes back and sends the first story and so it carries on between the top 2 headlines.
Is there a way I can force the script to not go past the first line I'm trying to retrieve in the script so this back-and-forth can't happen?

Here's the proc I'm using:

Code:

proc getrtr {sock} {     global rtrurl rtrold     set headers [egghttp:headers $sock]     set body [egghttp:data $sock]     egghttp:cleanup $sock     foreach line [split $body \n] {       if {[string match "*52_*" $line]} {         set rtr [gettok $line 2 62]         set rtr [gettok $rtr 0 60]         set rtrurl [gettok $line 5 34]         if ($rtr != $rtrold)} {           putserv "PRIVMSG #channel :/0034,4 /0031,15 $rtr /00314,14 /003"         } else {           set rtrold $rtr         }       }     } }

Thanks for any help!

Statistics: Posted by NewzUK — Wed Jun 30, 2004 5:03 am