{
  # compile each test once...
  my %file_test = map { $_ => eval "sub { -$_ \$_[0] }" }
                   qw(r w x o R W X O e
                      z s f d l p S b c
                      t u g k T B M A C);

  sub FileCheck {
    my($file,$perm,$badness) = @_;
    die "invalid file test" unless exists $file_test{$perm};
    unless ($file_test{$perm}->($file)) {
      if ($badness eq 'die') {
        die "\nError (fatal) accessing $file: $!";
      } elsif ($badness eq 'warn') {
        warn "\nError (non-fatal) accessing $file: $!";
      }
    }
  }
}
[download]

This also makes it relatively simple to create "new" filetests, should you want to...

If you use eval "-$perm... I would advise checking $@ to see if you had an invalid filetest requested.

update: added $_ => so it works. Much apologies. (Also s/exsits/exists/)

Looks like eval "-$perm \$file" will do the trick.

Update: Since testing shows that it works, I made it a statement, not a question.

Update 2: $TIMTOWTDI = eval "-$perm \"$file\""

perl -pe '"I lo*`+$^X$\"$]!$/"=~m%(.*)%s;$_=$1;y^`+*^e v^#$&V"+@( NO CARRIER'

I find that explicit referencing of @_ inside of functions is problematic. It is too easy when modifying code to accidentally access this when you meant that. For which reason the two main styles you see go like:

sub FileCheck {
  my $file = shift;
  my $perm = shift;
  my $oot = shift;
  # etc
}
# or
sub FileCheck {
  my ($file, $perm, $oot) = @_;

  # etc
}
[download]

(I also don't much like StudlyCaps, but that is one of those "important irrelevancies". It is good to be consistent about naming patterns, but which consistent choice you make is irrelevant. InOtherWords I don't code that way, but there is nothing wrong with doing so.)

String eval works:

unless (eval "-$perm \$file") {
[download]

if not, then maybe what you want is eval "-$perm \$file"
--
Snazzy tagline here