> Not quite. I'm saying: "Unless you need fork you're probably > better off using a perl without PERL_IMPLICIT_SYS" [on Win32, > obviously]. There's no problem with having ithreads enabled; > it's PERL_IMPLICIT_SYS that requires perl's malloc to be disabled.
Got it. Ok, sorry to be so thick. > >Threading with a faster malloc sounds very nice. Anything I can do to > >motivate you on this? Single-malt maybe? ;-) > > > As above, I think you've mis-understood me (or I didn't explain > clearly). You can already have threaded perl with faster > malloc -- just be sure to disable PERL_IMPLICIT_SYS. You keep the threads > and perl's malloc. You only lose the fork() emulation. Allow me rephrase my comment: fork() with a faster malloc sounds very nice. Anything I can do to motivate you on this? Single-malt maybe? ;-) Thanks for clarification, Yves
