Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Perl: porters

Cleanup vfork debris?

 

 

Perl porters RSS feed   Index | Next | Previous | View Threaded


schwern at pobox

May 4, 2012, 3:59 PM

Post #1 of 2 (55 views)
Permalink
Cleanup vfork debris?

In answering a StackOverflow question, I did a quick grep for what Perl
actually does with vfork after going through the trouble detecting it. The
answer appears to be: nothing.

Looks like it was eliminated 11 years ago by Sarathy.
https://github.com/mirrors/perl/commit/52e18b1f277416a33dff2c066a83fdab0520a2d7

Any strong objections to eliminating the associated vfork debris? Looks like
config stuff, hint files, and some special VMS code can all just be deleted.


--
THIS I COMMAND!


craig.a.berry at gmail

May 6, 2012, 7:18 AM

Post #2 of 2 (46 views)
Permalink
Re: Cleanup vfork debris? [In reply to]

On Fri, May 4, 2012 at 5:59 PM, Michael G Schwern <schwern [at] pobox> wrote:
> In answering a StackOverflow question, I did a quick grep for what Perl
> actually does with vfork after going through the trouble detecting it.  The
> answer appears to be: nothing.
>
> Looks like it was eliminated 11 years ago by Sarathy.
> https://github.com/mirrors/perl/commit/52e18b1f277416a33dff2c066a83fdab0520a2d7
>
> Any strong objections to eliminating the associated vfork debris?  Looks like
> config stuff, hint files, and some special VMS code can all just be deleted.

I don't object but I wasn't sure on a quick glance how much of what's
left has to do with calling vfork() from Perl (which I think you're
right has been gone a long time) and how much with making vfork()
slightly safer when called from XS.

Perl porters RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.