On Fri, 2005-11-25 at 10:54 +0100, Tels wrote: > You didn't say which Perl version you are using. Also, have you tried with > a non-threading Perl?
I've had this problem on perl 5.8.5 and 5.8.6. I don't think the perl version effects it, I think it is some strange interaction between SDL and perl. I'm still trying to cook up a reliable test case example script. I don't have a perl compiled with usethreads=undef (by perl -V), but the script in question is not a threaded perl script (doesn't "use threads"). I realize that I'm still using a perl with multiplicity enabled, but I don't really see a way around that going forward, since the trend seems to be to have multiplicity enabled if the target platform supports threading -- it's kind of odd to require a specially compiled perl version in order to use SDL_perl. Looking at the SDL source, if you use timers on a platform that supports threads, it seems like timers will be implemented with threads (this is an implementation detail in SDL). I don't really see a way to disable that, but I have not stared at the SDL code long enough. (It would be really nice if you could wait for events with a timeout, that would make things a lot simplier without having to eat CPU constantly calling poll all the time). -- Andy <[EMAIL PROTECTED]>
