On Wed, Oct 13, 2004 at 08:30:39AM +0200, [EMAIL PROTECTED] wrote:
> Aha. I thought someone might want this...
>
> It doesn't 'use threads' (or rather require), of course, unless ithreads has been
> configured.
>
> The issue I see, where you have a choice, is that someone might wish to use threads
> further down the line, and the debugger simply needs to have this setup right early
> on. Just like using Term::ReadLine or IO::Socket or Term::Rendezvous, etc. , these
> need to be setup on at the start, and imho (very small o ;), doing this later will
> be a real bucket of worms.
>
> Or do you think it might be ok to just complain if there is an attempt to use
> threads, when it has been explicitly turned off? Perhaps it could be a runtime
> (commandline) option to turn it on in the first place? Thoughts?
Random thoughts:
If a commandline option would do it, that sounds good. Otherwise, perhaps
skip the use threads (and complain if there's a later attempt) unless
$ENV{PERL5DB_THREADED} is true (and have perl.c set PERL5DB_THREADED if
you say -dt).
