No, I don't think so. I am not sure what your code has to do with anything. If you flush STDOUT after every write, that is same as un-buffering it.

Consider Program 1:

#!/usr/bin/perl
use warnings;

for my $i (1..5)
{
   $x+1; # here just to throw an error to STDERR
   print "$i\n";
}

__END__
Useless use of addition (+) in void context at C:\Projects_Perl\testin
+g\demoStdErrorTiming1.pl line 6.
Name "main::x" used only once: possible typo at C:\Projects_Perl\testi
+ng\demoStdErrorTiming1.pl line 6.
Use of uninitialized value $x in addition (+) at C:\Projects_Perl\test
+ing\demoStdErrorTiming1.pl line 6.
Use of uninitialized value $x in addition (+) at C:\Projects_Perl\test
+ing\demoStdErrorTiming1.pl line 6.
Use of uninitialized value $x in addition (+) at C:\Projects_Perl\test
+ing\demoStdErrorTiming1.pl line 6.
Use of uninitialized value $x in addition (+) at C:\Projects_Perl\test
+ing\demoStdErrorTiming1.pl line 6.
Use of uninitialized value $x in addition (+) at C:\Projects_Perl\test
+ing\demoStdErrorTiming1.pl line 6.
1
2
3
4
5
[download]

Consider Program 2:

#!/usr/bin/perl
use warnings;
$|=1;               ### BIG DEAL HERE ### Unbuffers STDOUT

for my $i (1..5)
{
   $x+1; #here just to throw an error to STDERR
   print "$i\n";
}

__END__
Useless use of addition (+) in void context at C:\Projects_Perl\testin
+g\demoStdErrorTiming2.pl line 7.
Name "main::x" used only once: possible typo at C:\Projects_Perl\testi
+ng\demoStdErrorTiming2.pl line 7.
Use of uninitialized value $x in addition (+) at C:\Projects_Perl\test
+ing\demoStdErrorTiming2.pl line 7.
1
Use of uninitialized value $x in addition (+) at C:\Projects_Perl\test
+ing\demoStdErrorTiming2.pl line 7.
2
Use of uninitialized value $x in addition (+) at C:\Projects_Perl\test
+ing\demoStdErrorTiming2.pl line 7.
3
Use of uninitialized value $x in addition (+) at C:\Projects_Perl\test
+ing\demoStdErrorTiming2.pl line 7.
4
Use of uninitialized value $x in addition (+) at C:\Projects_Perl\test
+ing\demoStdErrorTiming2.pl line 7.
5
[download]

Program 1's error messages come out right way while stdout messages come later because the stdout's filehandle's output buffer is not ready to be "flushed", "printed".

Program 2's error messages are interleaved with "normal" prints because the normal prints are being prematurely flushed out. There is a big,(can be HUGE) performance penalty for this but, this makes debugging easier.

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.