On 29 Jan 2007, at 12:41, Michael G Schwern wrote:
Umm, yeah. I was wondering about that.
Sorry for the confusion. The patch serves two purposes:
1) It makes it possible for people to try TAPx::Harness and easily
disable it if they run into problems
2) It's part of me working out the role of the
TAPx::Harness::Compatible code. I'm trying to identify
cases where extant code can easily be made compatible with the
new TAPx::Harness interface as part
of understanding how the compatibility layer is likely to be used.
--
Andy Armstrong, hexten.net
