Actually, the waitports is defined as an empty block at the begining of the
script:
waitports: []
then later...
waitports: [irc-open-port]
I only do the probing when I excape from the programs execution on the
waitports block. I usually do that while waitports contains the appended
dcc ports. Im not to worried about the ports as I have the user-data path
within the port object. I also downloaded the internet draft for MSN
Messenger Protocol version 1.0 today and hope to add that to my irc bot so
that it can relay internet messages within the bot to someones MSN account.
I should run into a whole batch of new questions for everyone. Move over
eggdrop....soon a better alternative will be here.
----- Original Message -----
From: "Elan" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, January 11, 2001 11:31 AM
Subject: [REBOL] Re: Back to the Advanced Port stuff again
> Hi Paul,
>
> you wrote:
> > interesting enough is that when we did a print first waitports we
returned
> > 'irc-open-port. When we stepped through the waitports block to the next
> > position and did a probe next first waitports we did not return the word
> > which we believe was because the script was reducing before appending
the
> > port object to the block at some point.
>
> That behavior is indeed very interesting. Do you happen to still have
> the code segment that exhibited this behavior? What I would be
> interested in is the line in which irc-opent-port is added to waitports,
> the lines in which other port objects are added to the port, and the
> line in which the waitports block is probed, first with "firts", and
> then with next.
>
> TIA,
>
> Elan
> --
> To unsubscribe from this list, please send an email to
> [EMAIL PROTECTED] with "unsubscribe" in the
> subject, without the quotes.
>
--
To unsubscribe from this list, please send an email to
[EMAIL PROTECTED] with "unsubscribe" in the
subject, without the quotes.
