Some modules need to know if they are running in a threaded enviroment. My
idea is to make use threads; add a Config option Config::isthreaded or
similar so that modules can do if(Config::isthreaded) { do thread specific
stuff here }:
This forbids the inclusion of threads after the compilation phase. I don't
see any reason to allow eval "use threads;" outside the compilation phase.
This also lets module using CLONE to know if they are running under ithreads
or under pseudo fork.
Artur
