Several options:

• Interrupt the test at that point. The harness should catch it.
• Run the test manually (perl t/pty.t) and capture the output. It may give you a better idea of what's going on.
• If that's the only test that fails, install it anyway.
• Send any failure messages to the author.
• Optionally, fix the error yourself (by looking in the test), and send the author a patch. :)

If you can swing the last option, do it. Otherwise, it's probably just an unportable assumption on the author's part. (Getting terminal stuff right across platforms is tough, though SCO should be a lot closer to POSIX than either Win32 or MacOS.)

---

---

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.