Various notes for those who are curious. Please remember that the parser is still alpha software! I have no plans to label it beta until such time that I know all core features are added. With luck, they'll be working, too.

Feedback appreciated.

• Rename all boolean methods with 'is_'.
  
  

  I've done this in my local repository and have deprecated the original method names. They will now issue a warning but will not be removed until 1.00. For example:

  if ( $test->passed ) { ... }

  Has become:

  if ( $test->is_ok ) { ... }

  We still have two boolean methods which don't begin with 'is_'. $test->has_todo and $test->has_skip. I don't feel entirely comfortable with this.

• Write TAPx::Harness.
  
  

  This should now be relatively straightforward. You'll still have plenty of control over the output merely by passing in callbacks to override default behavior.

• Make it work on older versions.
  
  

  Much work has already been done in this regard.

• Make tprove offer almost identical functionality and output as prove.

  I plan to add support for reading a .tproverc.

  Aside from duplicating the current behavior, I also plan to some new switches:

  • -c. --color Run tests with colored output.
    
    

    By default, if Term::ANSIColor is installed, will show failing tests in red. Controllable via .tproverc.

  • -f, --failures Only show failing tests.
  • -m, --match Only tests which match the --match regex will be run.
    
    

    This might seem odd, but more than once I've found it useful if I want to run, for example, my 'customer' tests.

• Find people with VMS or MacPerl who are willing to test the parser.
  
  

  Currently, I'm pretty sure I'll get test failures on both. I initially tried to cargo-cult in the code from Test::Harness, but since I couldn't reliably test it, I stopped.

---

---

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.