Thursday, October 10, 2002, 12:39:31 AM, you wrote:
>> > add READ/WRITE-CHAR/BYTE-SEQUENCE-NO-HANG (that's 4 functions)
>> > which, on entry, put the socket (if that was a socket stream)
>> > into a non-blocking mode and do the I/O;
>> Of course it's just a matter of design. But sockets thing not using
>> different function names, it uses socket modes to not duplicate all
>> functions. The question is, will be there more blocking-dependent
>> functions in the interface ?
> sorry, I don't understand the question.
I mean will we need then (someday) close-no-hang, write-integer-no-hang,
I was recently signed up for English courses, you'll see how my
English will improve...
>> > before the return, you will need to put the socket back into blocking
>> > mode (see make_HANDLER_frame/unwind_HANDLER_frame).
>> Didn't get it now.
Thanks, understood it.
>> Sheduling it for when my improved ultimate shortcut resolver will work
>> (it grows... now I think shouldn't it handle m3u playlists ?).