print goes to STDOUT, and warn goes to STDERR. The text on STDOUT is parsed as TAP. So if one of your many printf() happened to print text to STDOUT that could be interpreted as unsuccessful TAP (or just inject content into the stream of valid TAP that breaks its syntax), then this could be a legitimate failure. Afaik, STDERR is always seen as logging data and never parsed as TAP. Anything your script writes to STDOUT should be prefixed with a "# " to ensure it can't be parsed as TAP. Don't forget if your printf wraps lines, each line would need to begin with "# ". In general you should just remove any printing to STDOUT in your XS code. Is there any reason to use printf instead of warn for diagnostics?

---

---

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.