No-wait modifies the behaviour of 'copy, not 'wait. Copy doesn't block, but returns immediately with an empty string if there is no data.
BTW: I found that it works best to have buffering on in TCP ports. --Maarten Paul Tretter wrote: >What is the purpose of no-wait. Doesn't seem work for me. Isn't no wait supposed to >return immediately. > >For example: > >Shouldn't a forever loop that has the following code always be printing instead of >only once the port has received data? > >port: open/direct/no-wait tcp://:7000 >x: 0 >forever [ > print x + 1 > x: x + 1 > data: first wait port >] > >I would like to see it continuously printing the value of x instead of only after it >receives data on the port. So what does no-wait accomplish? > >Paul Tretter > > > > > > >--- >Outgoing mail is certified Virus Free. >Checked by AVG anti-virus system (http://www.grisoft.com). >Version: 6.0.577 / Virus Database: 366 - Release Date: 2/3/2004 > > -- To unsubscribe from this list, just send an email to [EMAIL PROTECTED] with unsubscribe as the subject.
