Uri Guttman <[EMAIL PROTECTED]> writes:
>> "UG" == Uri Guttman <[EMAIL PROTECTED]> writes:
>
> UG> i recall seeing someone mentioning that event.pm now runs under
> UG> windows. is that true? is there a binary for it? activestate lists
> UG> event.pm as a ppm but it only shows various unix f
Robert Urban <[EMAIL PROTECTED]> writes:
>Hi Nick,
>
>You wrote:
>> Joshua N Pritikin <[EMAIL PROTECTED]> writes:
>> >- Forwarded message from Robert Urban <[EMAIL PROTECTED]> -
>> >
>> >To: [EMAIL PROTECTED]
>> >Subject: Event and non-Event signal handlers on Linux
>> >From: Robert Urban <
Joshua N Pritikin <[EMAIL PROTECTED]> writes:
>- Forwarded message from Robert Urban <[EMAIL PROTECTED]> -
>
>To: [EMAIL PROTECTED]
>Subject: AF_UNIX sockets and Event.pm
>From: Robert Urban <[EMAIL PROTECTED]>
>
>
>Hello,
>
>I have written a simple script which uses Event->io on an UNIX so
Joshua N Pritikin <[EMAIL PROTECTED]> writes:
>- Forwarded message from Robert Urban <[EMAIL PROTECTED]> -
>
>To: [EMAIL PROTECTED]
>Subject: Event and non-Event signal handlers on Linux
>From: Robert Urban <[EMAIL PROTECTED]>
>X-Seen: false
>X-ID: [EMAIL PROTECTED]
>
>Hallo Joshua,
>
>hmm.
C98\bin\cl.exe' : return code '0x2'
>> Stop
>>
>> I don't understand what are mistakes here.
>> I would like you to help me for correcting this package on windows platform,
>because it's necessary for my project.
>>
>> Thank you very much for your support.
>> My I please hear from you soon?
>
--
Nick Ing-Simmons
http://www.ni-s.u-net.com/
Joshua N Pritikin <[EMAIL PROTECTED]> writes:
>On Tue, May 14, 2002 at 10:04:51AM +0100, Nick Ing-Simmons wrote:
>> >In Event.xs, I change _loop() to:
>> >
>> >PROTOTYPE: ;$
>> >CODE:
>> >double maxtm = 60;
>> >if (
>
>To do this, one would add the following to their script:
>
>Event->timer(interval => 5, cb => sub{unloop;});
>
>then change their Event::loop; line to
>while (1) {
>Event::loop;
>}
>
>Brad
--
Nick Ing-Simmons
http://www.ni-s.u-net.com/
this fixed is to have signal handler write()
to a pipe that is in the select() list rather than just set a flag.
--
Nick Ing-Simmons
http://www.ni-s.u-net.com/
. perl's signal handling is well known to be unsafe.
perl5.7.1+ has safe signal handling.
>
>the way to handle that properly is to check for any pending signals
>before you enter the select call (while blocking any from coming in) and
>then checking after the select returns. this can only be done correctly
>in C.
>
>uri
--
Nick Ing-Simmons
http://www.ni-s.u-net.com/
Barries <[EMAIL PROTECTED]> writes:
>On Mon, Jan 29, 2001 at 10:46:07PM +0000, Nick Ing-Simmons wrote:
>> Barries <[EMAIL PROTECTED]> writes:
>> > Nick
>> >Ing-Simmons mentioned that there might be some possibility of and
>> >interest in port
Barries <[EMAIL PROTECTED]> writes:
>
>So, is anyone working (really) on this, thinking about it, or interested
>in contributing advice/time/whatever to such an effort? Nick
>Ing-Simmons mentioned that there might be some possibility of and
>interest in porting the new pol
?
I prefer the latter - it makes it more method-call-like.
--
Nick Ing-Simmons
t stable, now it is
I have other things top of my interest pile.)
>or CORBA. No doubt there are other popular libraries without Event
>support too.
--
Nick Ing-Simmons
Uri Guttman <[EMAIL PROTECTED]> writes:
>>>>>> "SL" == Steve Lidie <[EMAIL PROTECTED]> writes:
>
> SL> Nick Ing-Simmons wrote:
> >>
> >> Steve Lidie <[EMAIL PROTECTED]> writes:
> >> >
> &g
Steve Lidie <[EMAIL PROTECTED]> writes:
>
>Preliminary testing shows that Perl's native select() works OK on Win32
>sockets.
Hmm, even for listen sockets?
>Perhaps Tk::Event could be used for everything else.
--
Nick Ing-Simmons <[EMAIL PROTECTED]>
Via
Uri Guttman <[EMAIL PROTECTED]> writes:
>>>>>> "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 th
t subsystem.
>
>any comments or thoughts are welcome here. condolences are welcome
>too. i wanted to keep stem a pure unix system for a while but if this
>big potential customer buys in, i have to support redmond asap.
>
>thanx,
>
>uri
--
Nick Ing-Simmons <[EMAIL PROTECTED]>
Via, but not speaking for: Texas Instruments Ltd.
shift - easy
pop - hard
--
Nick Ing-Simmons
and
that is looking very tight on its own (I have not really started yet - panic!)
If someone else wants to have a try I am more than willing to give advice
and help with trickier bits. I will/can not change to Event scheme
in mainstream Tk distribution until Event is table on Win32.
--
Nick Ing-Simmons
{
$self->{$pkg}; # just return it.
}
>
> $self->{$pkg} = shift if @_ ;
> $self->{$pkg};
That does the hash lookup twice for the set case, while the else form
only does it once.
--
Nick Ing-Simmons <[EMAIL PROTECTED]>
Via, but not speaking for: Texas Instruments Ltd.
et so can be inherited by (almost) everything.
--
Nick Ing-Simmons <[EMAIL PROTECTED]>
Via, but not speaking for: Texas Instruments Ltd.
Paul Moore <[EMAIL PROTECTED]> writes:
>From: Nick Ing-Simmons [mailto:[EMAIL PROTECTED]]
>>
>> It does not mention that in the book I have - is your source
>> either empirical or definitive ?
>
>MSDN - does that count as apocryphal? :-)
>
>>From the
ther empirical
or definitive ?
>This doesn't seem like a lot to me - is it likely to
>be an issue (do select() and/or poll() have similar limits?)
--
Nick Ing-Simmons
Graham Barr <[EMAIL PROTECTED]> writes:
>On Tue, Mar 21, 2000 at 04:10:45PM +0000, Nick Ing-Simmons wrote:
>> But when Event says "handle is readable" how is perl code going to
>> do its IO to read it? - right now <$fh> or even sysread($fh,...)
>> ca
Graham Barr <[EMAIL PROTECTED]> writes:
>On Tue, Mar 21, 2000 at 04:10:45PM +0000, Nick Ing-Simmons wrote:
>> But when Event says "handle is readable" how is perl code going to
>> do its IO to read it? - right now <$fh> or even sysread($fh,...)
>> ca
Paul Moore <[EMAIL PROTECTED]> writes:
>From: Nick Ing-Simmons [mailto:[EMAIL PROTECTED]]
>>
>> long
>> Lang_OSHandle(fd)
>> int fd;
>> {
>> #ifdef WIN32
>> return win32_get_osfhandle(fd);
>> #else
>> return fd;
>> #end
quot;socket not readable" does NOT mean "No XEvents pending".
Also IIRC this is TCP socket so an XEvent may not be complete.
You also need to XFlush() pending outgoing requests prior to the select().
--
Nick Ing-Simmons <[EMAIL PROTECTED]>
Via, but not speaking for: Texas Instruments Ltd.
ocess makes it necessary to have a queue of
events or you need to re-enter the "get_events" thing
at the appropriate point - skipping the ones which have
had their turn - to be "fair".
--
Nick Ing-Simmons <[EMAIL PROTECTED]>
Via, but not speaking for: Texas Instruments Ltd.
n async mode.
So we are stuck with stdio layer until such time as we rewrite PerlIO
to use native Handle level APIs.
--
Nick Ing-Simmons <[EMAIL PROTECTED]>
Via, but not speaking for: Texas Instruments Ltd.
;s own C "stdio" runtime (which perl currently uses) cannot work with
asynchronous IO.
--
Nick Ing-Simmons <[EMAIL PROTECTED]>
Via, but not speaking for: Texas Instruments Ltd.
Uri Guttman <[EMAIL PROTECTED]> writes:
>>>>>> "NI" == Nick Ing-Simmons <[EMAIL PROTECTED]> writes:
>
> NI> Uri Guttman <[EMAIL PROTECTED]> writes:
> >>
> >> try looking at how perl does select (4 arg) under winblows.
Uri Guttman <[EMAIL PROTECTED]> writes:
>
>try looking at how perl does select (4 arg) under winblows.
It only works for Sockets in blocking mode. It is near useless.
--
Nick Ing-Simmons <[EMAIL PROTECTED]>
Via, but not speaking for: Texas Instruments Ltd.
erl code.
_*BUT*_ the innermost "wait for next event" needs to be very OS specific.
On modern UNIX is fundamentally poll() which waits for selected events.
On Win32 it wants to be MsgWaitForMultipleObjects() - but also work
on Win9X and WinCE !
>
>But don't dismiss Win32. Event is needed more (in some sense) there than on
>Unix. But the Win32 Perl population is small, and the number who really know
>both Win32 and Unix, and who have the time to work on it is even smaller.
--
Nick Ing-Simmons <[EMAIL PROTECTED]>
Via, but not speaking for: Texas Instruments Ltd.
ot;statement" that writes $foo many times.
I think most perl o_ps_ will (in the absence
of ties or other C-level magic) only write it once. You cannot
tell what XS code might do, or ties.
--
Nick Ing-Simmons <[EMAIL PROTECTED]>
Via, but not speaking for: Texas Instruments Ltd.
max_wait or min_idle ?)
Just make the docs spell it out is enough...
--
Nick Ing-Simmons
n minutes?
I would have though "when idle or in not more than 30s" is what one
would want - which has a "max" feel to me ...
--
Nick Ing-Simmons
course you should also consider if Event->io should use AUTOLOAD or
>if Event::io should just call a register method to create the sub, thus
>doing away with AUTOLOAD all together.
Tk with explcit require does the later - i.e. Tk/Foo.pm
drops a Tk::Widget::Foo into the name space (via an inherited 'Construct'
method but that is detail).
--
Nick Ing-Simmons
without threads.
Threads seem to need Event ...
Thus I suspect that what it really needs is ActiveState (e.g. Sarathy),
to need something working ...
--
Nick Ing-Simmons
t;
>That sounds fine. I'm probably not going to touch threads until 5.6 is
>released.
That is sad - it means that if Threads and Event don't
work together right most folk will have to wait for 5.7.
The whole point of beta process is so modules can test against them ;-)
--
Nick
39 matches
Mail list logo
