Here's what I suggest that you do.

use strict;
use warnings;

use Clue::ByFour;
use Existing::Client;

my $clueX4 = new Clue::ByFour;
my $client = new Existing::Client;

$clueX4->add("rusty nail");
$clueX4->target($client);
for (0..1000) {
    $clueX4->swing();
}
[download]

Seriously. You need to at least make an attempt to enlighten the client about the Right Way (TM) to do this. You may THINK you have control over the format of the file, but some day down the line (sooner rather than later) and you or whoever works on this after you is in for a world of hurt. Security people are NOTORIOUSLY stupid about this sort of thing...they have policies that they have sat around and dreamed up and never even really considered the intelligence of.

You should have enough pride in your work to be SERIOUSLY po-ed about being asked to write shoddy 2nd rate code because of PHB's in the first place.

---

---

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