Re^5: multi-threaded win32::console

Am I not using strict in all examples (even the admittedly horrible original post) above?

You are putting it in the code you post, but you obviously aren't using it when you run the code on your machine, else you would be seeing and correcting these errors and warnings--not me.

Trust me when I say that the versions of Perl and XP will not be causing the warnings I reported in the code from the post to which I replied.

When I correct the logic errors I detailed, then I get this output:

C:\test>632320
same values, different keys: A->b
same values, different keys: A->h
same values, different keys: A->s
same values, different keys: A->t
same values, different keys: A->d
same values, different keys: A->f
same values, different keys: A->h
same values, different keys: A->w
same values, different keys: A->c
same values, different keys: A->d
same values, different keys: A->f
same values, different keys: A->p
same values, different keys: A->c
same values, different keys: A->g
same values, different keys: A->o
same values, different keys: A->v
same values, different keys: A->o
same values, different keys: A->g
same values, different keys: A->j
same values, different keys: A->n
    1/177  .
[download]

And if I comment out the print line producing that "same values, ..." output I get

C:\test>632320
    1/177  .   11/0
[download]

That's obviously only the final state when the program ends. I see the values changing as the program progresses. And that I think is the answer to your original question. Mixing consoleIO and prints means that the latter is overlaying the former and causing the screen to scroll.

You should opt for using one or the other. Or, clear the screen first, write your status information to the top line whilst saving and restoring the current cursor postion before and after each write, and then your print statements can scroll down the screen and the status information stays fixed.

Personally, I think that avoiding mixing them is the easiest option.

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.

"Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."

Comment on Re^5: multi-threaded win32::console Select or Download Code

Replies are listed 'Best First'.
Re^6: multi-threaded win32::console by goibhniu (Hermit) on Aug 14, 2007 at 07:30 UTC
I feel I must protest. Copying the code from Re^2: multi-threaded win32::console into a new file and running it yields for me: `C:\chas_sandbox>test.pl 1/177 . 5/8 7/5 4/23 C:\chas_sandbox>` [download] and I see no errors or warnings. Please tell me why you see more errors and warnings than I do. (I'm sure that you see some errors and warnings like the lack of $k because of your advanced wisdom; please tell me why your PERL shows you more than my PERL shows me.) I surely don't expect you to be debugging compare for me - I sincerely thought it was working on my system without problem. Perhaps if I can learn this wisdom, I won't post bad code so much.	[reply] [d/l]
Re^7: multi-threaded win32::console by BrowserUk (Patriarch) on Aug 14, 2007 at 09:21 UTC
Try adding `use warnings;` after the `use strict;` line in the code from Re^2: multi-threaded win32::console and then run it... 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. "Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."	[reply] [d/l] [select]
Re^8: multi-threaded win32::console by goibhniu (Hermit) on Aug 14, 2007 at 12:06 UTC
Ah, mea culpa! I thought that `#!/usr/bin/perl -w` would do it regardless of platform. I now see in the book of perlrun that I would have to trick my OS into doing that in an OS specific way. I'll return after some more debugging.	[reply] [d/l]