As a Win32er, I am glad to see fork() and ithreads in the latest perl!


One thing that I feel is missing and *might* be easy to add
is to also emulate exec() --I know there is already an exec(), but
in all of the unix/linux examples and coding techniques they use
fork()->exec() to start a new process quickly (since the fork() uses
COW, it doesn't actually do anything, and just does the exec in the
new process).

I would like to have, under win32 anyway, the ability to call fork()
and then exec() and have it create a new ithread w/o any data copying.
It would just be a new thread that loads the perl interpreter.
With that new thread, it would probably just load the standard modules,
and you would have to add any others you wanted manually (and IPC would
be your responsibility).

Since creating processes under win32 is very slow (in comparison anyway),
and most win32 programs are multi-threaded, this would give perl the
ability to better perform on this platform (_MY_ opinion anyway ;-)

Does this make sense to you ithreaders?  And is there a better way
to describe it and the benefits before asking the p5p list???

thanks!!!


--

Reply via email to