This is probably the reason why many of us say "don't use threads for this task".

Even though you admit to having made little (no?) use of threads?

If you encountered a bug in a regex, that allowed the regex to work but causes a warning during global destruction, would you advocate the replacement of all regexes using character by character comparisons and huge if/else cascades?

Eg. You'd advocate if( $string =~ m[C\d\[A-Q]] ) { with

my $currentChar = substr( $string, $n, 1 );
if( $currentChar eq 'C' ) {
    $currentChar = substr( $string, ++$n, 1 );
    if( $currentChar eq '1' ) {
        $currentChar = substr( $string, ++$n, 1 );
        if( $currentChar eq 'A' ) {
        ...
        ...
        ...
        ...

        elsif( $currentChar eq 'B'
        ...
        ...
        ...
        ...
    }
    elsif( $currentChar eq '2' ) {
        ...
        ...
        ...
        ...
    }
    elsif( $currentChar eq '3' ) {
        ...
        ...
        ...
        ...
    }
    elsif( $currentChar eq '4' ) {
        ...
        ...
        ...
        ...
    }
    elsif( $currentChar eq '5' ) {
        ...
        ...
        ...
        ...
    }
    elsif( $currentChar eq '6' ) {
        ...
        ...
        ...
        ...
    }
    elsif( $currentChar eq '7' ) {
        ...
        ...
        ...
        ...
    }
    elsif( $currentChar eq '8' ) {
        ...
        ...
        ...
        ...
    }
    elsif( $currentChar eq '9' ) {
        ...
        ...
        ...
        ...
    }
    else {
        die "The second char was not in range '1' thru '9';
    }
}
else {
   die "The first character didn't match 'C'";    
}
[download]

Because that is the logical equivalent of your advice!

Or might you suggest working around the problem, and report the error, in the hope that the regex engine would get fixed?

Because that is the logical equivalent of your advice!

No. A construed analogy is not a logical equivalent.

My advice is to go with the framework, and try to use features of the framework rather than bending it, or mix in stuff which might lead to problems.

It just so happens that Tk can be used together with threads, but it wasn't written using threads - has it even been designed with threads in mind?

The OP was about a Tk problem, so I have posted a solution which works making use of Tk and its features. It was not me who was reaching for something entirely different, but you!

My solution might induce the wish to get a deeper understanding of how Tk works, and how to use it's lesser known internals directly - your solution of using threads just avoids a black spot which isn't in the toolkit, but in the knowledge of its user, and places on him the intellectual weight of understanding how's that thread stuff works and how to avoid pitfalls combining both... I remember you wrote something along that lines in a fine post elsewhere... ;-)

--shmem

_($_=" "x(1<<5)."?\n".q·/)Oo.  G°\        /
                              /\_¯/(q    /
----------------------------  \__(m.====·.(_("always off the crowd"))."·
");sub _{s./.($e="'Itrs `mnsgdq Gdbj O`qkdq")=~y/"-y/#-z/;$e.e && print}