My guess is it's a function of the language. If I write an
equivalent program in python, the behavior on windows is
totally ordered, unlike perl. So my guess is there is a
problem with perl's thread implementation in windows.
I've also noticed that if I start a thread in a perl
program that is qui
$Bill Luebkert wrote:
> Mathieu Longtin wrote:
>>STDERR is unbuffered by default (that's why I used it), and
> Supposed to be. Remember this is not UNIX. I don't assume.
And remember that it's not a function of the operating system anyway,
but of the language. (In this case, both Perl and the C
Mathieu Longtin wrote:
> STDERR is unbuffered by default (that's why I used it), and
Supposed to be. Remember this is not UNIX. I don't assume.
> apparently the threads are executing when they're supposed
> to, just not printing as they go.
Also remember that you're not dealing with the UNIX
STDERR is unbuffered by default (that's why I used it), and
apparently the threads are executing when they're supposed
to, just not printing as they go.
--- $Bill Luebkert <[EMAIL PROTECTED]> wrote:
> A couple of things to try. 1) Try opening a file for
> append in
> each thread and write your o
Mathieu Longtin wrote:
> I'm trying to use threads, but it seems threads are
> blocking the output on windows.
>
> I've included a sample program. It starts two threads, and
> then three threads proceed to print the time elapsed since
> the beginning of the process.
>
> On Windows, the two threa
I'm trying to use threads, but it seems threads are
blocking the output on windows.
I've included a sample program. It starts two threads, and
then three threads proceed to print the time elapsed since
the beginning of the process.
On Windows, the two thread print all their output when they
finis
