That seems to be a great Idea to me.

I like this concept, for it seems practical,
I've seen so many way of programming with a proven/therorical/formal design that were just unusable...

I REALLY like this method (paradigm?) beccause :

• The idea is simple (iterative 'enhance then check' step).
  
• The experience can be saved and transmitted (by describing refactoring recipe.)
• It seems that the process can be made partially automatic.
• It can be applyed to EXISITING project AND new ones.

However I'd definitly like to have more info on this (other links, books) and especially opinion of people who have been using it.
A step by step practical example of refactoring using Test, test::Harness on an existing code would be welcome too...

Anyway, thanks for this info, I've never been so excited about a programming method for long... (stephen++ ;-)

"Only Bad Coders Badly Code In Perl" (OBC2IP)

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.