Beefy Boxes and Bandwidth Generously Provided by pair Networks
good chemistry is complicated,
and a little bit messy -LW

Re^2: Strategies for maintenance of horrible code?

by GrandFather (Sage)
on Jul 12, 2006 at 08:38 UTC ( #560640=note: print w/replies, xml ) Need Help??

in reply to Re: Strategies for maintenance of horrible code?
in thread Strategies for maintenance of horrible code?

Actually, just writing the tests is often a damn fine way of finding bugs. No exactly what OP is after at the moment, but something that is at the forefront of my mind because I'm in the middle of writing a set of tests (in Perl :) for some XML processing C++ code and turning up a pile of bugs as I go.

However it does suggest another test avenue: write test harnesses for modules so that you can exercise them in isolation and better understand how they work. If the test harness ends up part of a regression test system so much the better.

DWIM is Perl's answer to Gödel
  • Comment on Re^2: Strategies for maintenance of horrible code?

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://560640]
Discipulus go to his cell to bookmark this
[haukex]: Well to be honest I just did a super search for "every should know floating" ;-)
[Discipulus]: floating was the keyword and.. to use supersearch is plus sign not a (plus) sin

How do I use this? | Other CB clients
Other Users?
Others drinking their drinks and smoking their pipes about the Monastery: (8)
As of 2017-06-26 20:59 GMT
Find Nodes?
    Voting Booth?
    How many monitors do you use while coding?

    Results (594 votes). Check out past polls.