Thanks for the comments.

We are using cvs, so that will be the source control tool, and we'll be creating a new branch for any development that needs to occur for the change to be succesful.

The acceptance tests are a bitch, but I'll give it the best go that I can, just some background, I came into this company a year ago, we're slowly moving everything to java from perl, but it's a slow enough process that we can no longer put off upgrading perl.

The code is quite simply some of the most horrible code that I've seen, the guys that started this system off did not know perl very well at all, worse, they didn't know how to program (we've got 8000+ line INLINE scripts - no subs)

In addition, nothings documented, some of the code is stuff that just runs, hasn't been looked at forever, and nobody really knows what it's supposed to do. It's a major headache just trying to maintain the stuff, it would be good to get some tests written during this migration to help with the maintenance afterwards...

It should be a good time, and I do have the buy in for the timeframes, machine, etc..

---

---

• 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.