First eval is a dangerous function to be using as a modification of one of the evaled expressions could be ahmm...interesting. Instead why not have all your rules ( regex pattern or not) wrapped in accessor methods in a file called say rules.pl:

package Rules;

sub rule1 {
    shift =~ m/some_pattern/;
}
[download]

This will return true or false depending on whether the passed argument matches /some_pattern/. You use it like this:

require rules.pl

&do_something() if Rule::rule1($match_this_data);
[download]

Then set it up so that your script is part of a unique group called say 'foo' Your rules file can then be made readable only by this group and no one else, hence the only access is via the script and no one except root, the owner(you) and the script can read it.

cheers

tachyon

s&&rsenoyhcatreve&&&s&n.+t&"$'$`$\"$\&"&ee&&y&srve&&d&&print

---

---

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.