in reply to Re^2: Win32, fork and XS globals
in thread Win32, fork and XS globals
When using system() there remains the small problem of copying the state of the old process over into the new process. Especially copying over allocated external resources, like sockets and open file handles.
Of course, not copying has its problems too, if one part of the fork closes/deallocates a resource while the other part wants to keep it open. But I think the other direction is more common, that only one of the two forked instances will continue to access a resource. From that direction, using OS threads to emulate fork() makes sense.
|
|---|
In Section
Seekers of Perl Wisdom