use the 'preprocess ' option. Your other option is to mess with signals (see perlsig, %SIG) 
#!/usr/bin/perl -w
use strict;
use File::Find;

# scrap codeee

find( { wanted => \&wanted,
#        preprocess => \&preprocess,
      }, '/' );

BEGIN { use vars qw( $maxHit $Hit); $maxHit = 10; }
BEGIN { $SIG{__DIE__} = sub {
                my @d = @_;
                if($d[-1] eq "dying max $maxHit") {
                    warn "hit the max $maxHit";
                    return();
                } else {
                    warn(@_);
                    exit(1);
                }
            };
}

sub wanted {
    my $file = $_;
    print "$file\n";
    $Hit++;
    die "dying max $maxHit" if($Hit >= $maxHit)
}

## something like this 

sub preprocess {
   my @list = @_;
   my $diff = $maxHit - $Hit;
   warn "pre processing( $Hit, $maxHit, ".scalar(@list)." )";

   if($Hit > $maxHit ) {
      return ();
   }elsif( @list > $diff ) {
      warn "splicing";use Data::Dumper;
      @list = splice(@list,0,$diff);
      warn Dumper \@list;
   }

   return @list;
}

[download]
update: you better stick with the eval ( see Kanjis node above). I've been too signal happy lately ;)

update: please note that the preprocess option is not available everywhere (best upgrade File::Find)

I also feel that there ought to exist File::Find::breakout, which would basically stop find from executing anymore (return? ;)

UPDATE: after hastily posting this, which i still think is good idea, a couple of smart asses point out goto. Yeah well i'm not 0 for 2 so far ;)(dammit! sometimes solutions you know but don't love escape you)

 
______crazyinsomniac_____________________________
Of all the things I've lost, I miss my mind the most.
perl -e "$q=$_;map({chr unpack qq;H*;,$_}split(q;;,q*H*));print;$q/$q;"

In reply to Re: File::Find redux: how to limit hits? by crazyinsomniac
in thread File::Find redux: how to limit hits? by u914

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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! —
  • 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:
    & &amp;
    < &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.