|The stupid question is the question not asked|
Re^4: [FCGI.pm] - not threads-safe?by BrowserUk (Pope)
|on Aug 20, 2013 at 23:12 UTC||Need Help??|
Thread says its been reworked using threads:: for old code
Problem: Code designed to use Perl 5005threads isn't compatible with iThreads without considerable rework, if then.
Monkey patching Thread to be an alias for threads in the vain and frankly naive hope that it would allow code written to use the former to magically work was ... well; naive at best. Thread should have been consigned to the dustbin of history along with pretty much everything in that namespace, excepting Thread::Queue which should have been moved into the threads namespace.
So, the question is, does the presence of that single file in the FCGI distribution, that uses a long obsolete version of perl threading that never worked, and despite the fact that threading isn't mention in either the POD or the readme; and the only mention of threading in the C code is the use of a C thread to provide asynchronous IO for stdin; constitute a statement of support for the use of iThreads with FCGI?
You know the answer to that as well as I do. Which makes your contribution in this thread one big red herring guaranteed to waste people's time.
With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
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.