If you can supply a reproducible test case then no doubt others could test and determine if it is indeed an MSWin32-only issue.
Actually I can (and just have) tested it out on Ubuntu, perl-5.34.0 and it's the same issue.
Here's an Inline::C demo of the problem:
Firstly, with the printf() statement commented out:
use strict;
use warnings;
use Inline C => <<'EOC';
SV * foo( SV * in ) {
/* printf("# %s\n", SvPV_nolen(in)); */
return newSVpv(SvPV_nolen(in), 0);
}
EOC
my $ok = 1;
print "1..1\n";
for(1 .. 1000) {
my $n = int(rand(10000000));
$ok = 0 if foo("$n") ne "$n";
}
if($ok) { print "ok 1\n" }
else {
print "not ok 1\n";
}
__END__
I first run
perl try.pl to compile the script, and then I run:
$ perl -MTAP::Harness -e '$h = TAP::Harness->new(); $h->runtests("./tr
+y.pl");'
./try.pl .. ok
All tests successful.
Files=1, Tests=1, 0 wallclock secs ( 0.04 usr 0.01 sys + 0.06 cusr
+ 0.01 csys = 0.12 CPU)
Result: PASS
As you can see, everything is fine.
But if I then include the printf() statement and run
perl try.pl (to recompile the script), upon re-testing I get:
$ perl -MTAP::Harness -e '$h = TAP::Harness->new(); $h->runtests("./t
+ry.pl");'
./try.pl .. All 1 subtests passed
Test Summary Report
-------------------
./try.pl (Wstat: 0 Tests: 1 Failed: 0)
Parse errors: No plan found in TAP output
Files=1, Tests=1, 1 wallclock secs ( 0.11 usr 0.01 sys + 0.05 cusr
+ 0.02 csys = 0.19 CPU)
Result: FAIL
Cheers,
Rob
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.