Re^4: Win32, fork and XS globals


Keep It Simple, Stupid
	PerlMonks

Re^4: Win32, fork and XS globals

by syphilis (Archbishop)

on Oct 12, 2011 at 11:43 UTC ( [id://930985]=note: print w/replies, xml )

Need Help??

in reply to Re^3: Win32, fork and XS globals
in thread Win32, fork and XS globals

But, as Corion correctly points out, there are limitations that prevent it from being a transparent solution to porting forking programs to Windows

Yep - thanks Corion, Buk.

By way of belated (and incomplete) explanation, I was led down this path by a PDL::Graphics::PLplot test script which does a couple of forks.
That test script works fine on nix systems, but exhibits some odd behaviour and errors on Windows. Thing is, of course, that the plplot library sets some globals and is not thread safe - not an issue with fork() on nix, but, as I've finally managed to grasp, prone to error with fork() on windows ... simple as that !!

Cheers,
Rob

Comment on Re^4: Win32, fork and XS globals

Replies are listed 'Best First'.

Re^5: Win32, fork and XS globals
by BrowserUk (Patriarch) on Oct 13, 2011 at 01:17 UTC

prone to error with fork() on windows ... simple as that !!

Indeed. I wish there was some way to estimate how ~~many~~ few instances of *nix forking code that work under Windows ~~thanks to~~ despite the fork emulation.

It might then be possible to argue for its removal and that could only benefit threaded code, that is currently hamstrung by 'features' necessary for that emulation.

It's way too late for that of course, but...

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

"Science is about questioning the status quo. Questioning authority".

In the absence of evidence, opinion is indistinguishable from prejudice.

[reply]

In Section Seekers of Perl Wisdom