- Step back, calm down, pour hot tea, drink, breath in, breath out.
- Make specs for software, describe what the old script did in detail, do not leave things out.
- Now you have to choose
- You start learning Perl and come here to Perlmonks where we monks help you fix stuff and learn to write your own script so next time it breaks you'll know how to put 2 lines together to fix it and not have to rely on some 3rd party
- You make an ad on jobs.perl.org and pay someone to fix/write it for you
- Convince her to update the script for you and she's welcome to stop by Perlmonks to ask some questions if she needs help
As biohisham has mentioned I tend to think the last of the 3 options would be most likely to get you some results.
-
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.
|
