TAP::Parser should be *easier* to subclass

[Eric Wilhelm]

# from Steve Purkis
# on Saturday 07 June 2008 07:42:

>1. uses TAP::Base throughout

Ok, but I do suggest caution.  Adding consistency is good, but my main 
concern is that we may end up with a "foolish consistency" where the 
base is being pulled too many different directions.

>2. uses instance attrs for class names

Yes, with mutators.  Apply liberally.

>3. introduces 'make_<class>' methods

I take it that this acts as a point to override/inject options into the 
sub-object's constructor call?

>4. includes a short SUBLCASSING / CUSTOMIZING guide

Yes!  I suggest TAP/Harness/Customizing.pod.

The HACKING.pod is mostly my fault, but I may be the only person who 
ever made edits to it.  Please read carefully and with a grain of salt.  
We should probably add links in there, as well as notes on the internal 
details of the customization support and some cleanup.

For quick 'WTF?' questions, you might find Andy or me in #toolchain on 
irc.perl.org.

--Eric
-- 
So malloc calls a timeout and starts rummaging around the free chain,
sorting things out, and merging adjacent small free blocks into larger
blocks. This takes 3 1/2 days.
--Joel Spolsky
---------------------------------------------------
    http://scratchcomputing.com
---------------------------------------------------