Funny you should mention this, because that's just what my company is about to do. Here's why:

We have a Boatload of Shell scripts that control various parts of our processes. No standards, very hard to find what's broken when something changes, etc. We want to replace the functionalty of all these scripts with Perl modules and an overarching Perl program to call them, And we want to incorporate testing modules into the process up front so that we can enforce standards, know what's broken when we make changes, and make it easier for new folks to see what's going on.

I'd love to see if anyone has done something to automate some of the process, but I imagine we'll be doing a lot of the conversion manually, simply because there's a lot of garbage accumulated that needs cleared away.

Which is a long way of saying, good luck, and I look forward to other answers.

NovMonk

---

---

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