Re^4: Test::Harness bug ? ... or author idiocy ?

Not a bug in Test::Harness after all.

Cool ... creating bug reports always ends up in being more work than one anticipates.
Thank you !!

If I simply modify your code to include $|++; before the plan is printed then the script runs fine

I thought that print "1..1\n" should flush the buffer immediately (because of the "\n") without any need to increment $|.
And this notion is supported by the following one-liner that prints out a "." followed by a newline every second for 10 seconds:

$ perl -e 'for(1..10) {print ".\n"; sleep 1}'
[download]

whereas this next one-liner (as expected) prints nothing for 10 seconds, and then immediately prints out all 10 dots:

$ perl -e 'for(1..10) {print "."; sleep 1}'
[download]

I don't doubt that I'm missing something pretty basic ... and I shudder to think what the answer might be .... but I'll ask the question "what is it that I'm missing ?", anyway ;-)

Cheers,
Rob

Comment on Re^4: Test::Harness bug ? ... or author idiocy ? Select or Download Code

Replies are listed 'Best First'.
Re^5: Test::Harness bug ? ... or author idiocy ? by hippo (Archbishop) on Nov 06, 2021 at 13:53 UTC
Your trivial examples are printing to the shell, presumably in a terminal. That is what makes it default to autoflush. Redirect that output and it's a different story. Compare: `$ perl -e 'for(1..10) {print ".\n"; sleep 1}' \| sed -e 's/\./#/g'` [download] with `$ perl -e '$\|++; for(1..10) {print ".\n"; sleep 1}' \| sed -e 's/\./#/g +'` [download] See the excellent Suffering from Buffering (particularly the section Hot and Not Hot) for more on this. When something else is wrapping the STDOUT, like your test harness for example, then the autoflushing is no longer applied by default. Everything in Perl should still be printed in the right order but I expect that the `printf` output in the C part is bypassing the higher-level buffer (just a guess - I don't know enough about how Inline::C works to say for sure). 🦛	[reply] [d/l] [select]
Re^6: Test::Harness bug ? ... or author idiocy ? by syphilis (Archbishop) on Nov 06, 2021 at 23:25 UTC
Your trivial examples are printing to the shell, presumably in a terminal. That is what makes it default to autoflush. Redirect that output and it's a different story</> Yeah ... that (and other points you make) seems reasonable. Thanks. I think it has now been shown to be a case of "author idiocy". (Not surprising, really.) Cheers, Rob	[reply]