So I'm in a bit of a quandary has a discussion about updating old scripts in a production environment and how to deal with some of the social issues around it. One thing that I got out of the conversation is that there are three basic criteria to look at when contemplating a rewrite:

1. Do you need to rewrite the script to add functionality now or in the future? A rewrite to make it easier to update will save you time in the future.
2. Is the script a security hazard? Is it broken in some fundamental way that compromises your security?
3. Do you require a boost in efficiency to handle higher traffic loads?

It looks like you are in situation 1. You need to look at your current update and how likely is it that future updates will be needed?

oakbox

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.