[EMAIL PROTECTED] wrote:
1. To test the code, you need to change it.
2. Before changing the code, you should test it.
How do we resolve these two opposites ? We change as little as
possible.
*snip*
A lot of my more recent thoughts about testing and development have
come from a wonderful
--- Michael G Schwern [EMAIL PROTECTED] wrote:
I've thought things like that in the past, innocent refactorings, and
broke shit. Especially since they have to be done by hand (where's
my refactoring browser!?)
At absolute minimum, with a big ball of mud, you can do dumb high
level exact
Hi all,
The next devel version of TAPx::Parser is on its way to the CPAN. Note
that at least one change is backwards incompatible. Of course, this
has always been labeled ALPHA software and in any event, folks should
not have been relying on the TAPx::Parser::Results classname, but there
you
