Keeping a single copy of anything, with no backups, is only one step away from it being deleted and lost forever. Automations are supposed to do a lot of work with minimal effort. Working on a filesystem automation in proximity to files you care about and have no backups for is high risk behavior regardless of what language you used. Unless Perl itself malfunctioned, it did nothing it wasn't asked to do.

There are design choices in many languages that are pessimal for safety though; SQL has unguarded DELETE that can wipe out a table just by omitting a WHILE WHERE. Perl has > for clobber mode, and < for input mode, a syntactic throwback to shell scripting that has probably made it way too easy for people to mistakenly clobber files.

---

---

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.