Re: To override fork, or not to override fork

{
    use fork'a'sleepy'share;
    fork(); # special  fork here
}
fork (); # regular fork here
[download]

Comment on Re: To override fork, or not to override fork Download Code

Replies are listed 'Best First'.
Re^2: To override fork, or not to override fork by learnedbyerror (Monk) on Dec 22, 2011 at 09:10 UTC
Sub::Exporter::Lexical has definitely proved interesting. The scope does not extend to use packages such as Parallel::Forker. I did not think it would but I was hopeful :). But, I was able to sub-class Parallel::Forker and Parallel::Forker::Process and was able to implement fork using Sub::Exporter::Lexical One of the designed limitations of Sub::Exporter::Lexical is that is only exports subroutines. So, I am checking into some of the other Lexical modules available on CPAN Thanks for the pointer to Sub::Exporter::Lexical. lbe	[reply]
Re^2: To override fork, or not to override fork by learnedbyerror (Monk) on Dec 21, 2011 at 19:25 UTC
Very interesting! I haven't seen this module before. I need to think about how it could be cleanly used without having the same impact as overriding fork in main. Any tips? Can I place all of the subroutines in a scope with this used at the top so that only forks from within these subs would be affected? If so, would the scope extend to fork made by another module like Parallel::Forker?	[reply]