From: Sam S. <sd...@gn...> - 2000-05-12 14:22:06
|
>>>> In message <14619.14942.902991.367998@ragged> >>>> On the subject of "Re: [clisp cvs] 'clisp/src ChangeLog,1.755,1.756 constsym.d,1.79,1.80 stream.d,1.163,1.164 subr.d,1.53,1.54'" >>>> Sent on Thu May 11 18:12:23 EDT 2000 >>>> Honorable Don Cohen <do...@ni...> writes: >> Sam Steingold >> >> this function NEVER waits for input of output to BECOME available, it >> only waits for INFORMATION on IO AVAILABILITY to become available. >> >> This is not what my man page on select seems to say. But I can't >> tell from that page what causes it to return other than the timeout. >> Does it return when any of the watched FD's changes? In which case >> if output and input are already available on all of them it must >> wait for the timeout? I'm sorry but the man page seems less than >> clear on this too. it returns when it can answer the question on each stream given, or when the timeout occurs, whichever comes first. I am repeating it for the third time. Hey, is my English really THAT confusing? >> on text streams, SOCKET-STATUS + WRITE-LINE or READ-LINE should be okay. >> >> This is clearly nonsense. please try to be polite. Are you a native English speaker? You clearly have problems understanding my writing (English is a second language for me too). I said "should be okay", which is not the same as "is the right way". It means that text streams are *usually* written to / read from not byte-by-byte but line-by-line, so presence of a single character is indicative of availability of a whole line (banning network problems). >> Other than real multiple processes I see no alternative to >> checking before every character or byte read or written (unless >> you're willing to block). true. so? -- Sam Steingold (http://www.podval.org/~sds) Micros**t is not the answer. Micros**t is a question, and the answer is Linux, (http://www.linux.org) the choice of the GNU (http://www.gnu.org) generation. (let ((a "(let ((a %c%s%c)) (format a 34 a 34))")) (format a 34 a 34)) |