NAME

DESCRIPTION

It is fairly common to write tests that need to fork. Not all systems support forking. This library does the hard work of checking if forking is supported on the current system. If forking is not supported then this will skip all tests and exit true.

SYNOPSIS

useTest2::Require::Fork;...Codethatforks...

EXPLANATION

Checking if the current system supports forking is not simple. Here is an example of how to do it:

useConfig;sub CAN_FORK {return1if$Config{d_fork};# Some platforms use ithreads to mimic forkingreturn0unless$^Oeq'MSWin32'||$^Oeq'NetWare';return0unless$Config{useithreads};return0unless$Config{ccflags}=~/-DPERL_IMPLICIT_SYS/;# Threads are not reliable before 5.008001return0unless$]>=5.008001;# Devel::Cover currently breaks with threadsreturn0if$INC{'Devel/Cover.pm'};return1;}

Duplicating this non-trivial code in all tests that need to fork is error-prone. It is easy to forget bits, or get it wrong. On top of these checks, you also need to tell the harness that no tests should run and why.