[Ecls-list] Next step with MSVC

Julian Stecklina der_julian at web.de
Thu Aug 7 18:15:16 UTC 2008


Robin Lee Powell <rlpowell at digitalkingdom.org> writes:

> On Wed, Aug 06, 2008 at 03:24:44PM -0700, Robin Lee Powell wrote:
>> > Better alternatives are (depending on your use case) e.g. osicat
>> > or usocket.
>> 
>> Thanks.  For some reason I thought usocket didn't have a way to do
>> non-blocking I/O.  I see that I was wrong.
>
> Oh, it's waiting with a timeout that it doesn't do, sort of.  (I
> know it's in trunk.)  That's OK; sub-1-second sleep seems to work
> fine.  :)

The CL world is missing a portable high-performance (network) I/O
framework. :-/

Regards,
-- 
Julian Stecklina

Well, take it from an old hand: the only reason it would be easier to
program in C is that you can't easily express complex problems in C,
so you don't. - Erik Naggum (in comp.lang.lisp)




More information about the ecl-devel mailing list