My job consists of a mixture of both methods of writing perl. I write scripts that edit ada code, generate reports from information within the ada code, and generate reports from output of other programs. The normal development phase of perl scripts here is that the software leads realize they need something, ask for a script that generates the information that they need, and then expect the reports(or edits) done as quickly as possible.

What I try to do is write a one-shot that does what they want, but is open enough so that I can then use it as a base for a complete program that will be ready when they realize that they needed it more then once.

I find that this approach works well because it keeps the requesting lead happy, helps make maintaining the code easier, and it allows each lead to use it.

The only time that I don't write code that I can easly translate into a full program is when it will only be used as a one-liner called from a shell script with perl -e.

-xPhase

---

---

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