>>>>> "NI" == Nick Ing-Simmons <[EMAIL PROTECTED]> writes:
NI> The Tk event loop works (after a fashion) on Win32 and is a
NI> self-contained XS module Tk::Event (Tk uses Tk::Event rather than
NI> vice versa). The snag is that 'fileevent' is seriously flawed on
NI> Win32 - e.g. you cannot wait for a 'listen' socket to be readable,
NI> nor on pipes, nor console. Basically only 'data' sockets work.
NI> The PerlIO stuff is intended to allow that to be fixed the same
NI> way Tcl/Tk fixed it - by using per-handle versions of read() etc.
NI> rather than C run-times flawed faking of UNIX semantics.
well, i need the socket stuff in particular. how does the redmond
perl/tk handle that?
what is the status of the perlio stuff? could it be made into a
standalone XS module for an event core? if redmond has it own read calls
with event semantics (as i gather it does), it doesn't sound like it
would be too hard to make a proper event loop out of that. would it be
better to work from event.pm or from perlio as a base? in any case i
can't (and won't) do it personally. i would need to hire some win32
expert for this. i will let you know when/if this happens and i will
probably be able to pay very well for it. :)
uri
--
Uri Guttman --------- [EMAIL PROTECTED] ---------- http://www.sysarch.com
SYStems ARCHitecture, Software Engineering, Perl, Internet, UNIX Consulting
The Perl Books Page ----------- http://www.sysarch.com/cgi-bin/perl_books
The Best Search Engine on the Net ---------- http://www.northernlight.com
