problem one, covered in PAR::FAQ 
unless(caller)

[download]
Problem two 
$source_path = win_path($source_path);
$destination_path = win_path($destination_path);

if (!$destination_path)
{
    $destination_path = $source_path;
}

my @files = <$source_path\\*>;

my %seen;

my $search = 'while (<>) { study;';
$search .= "++\$seen{\$ARGV} if /\\b_$project_id\\b/;\n"; 
$search .= "}";

@ARGV = @files;
undef $/;
eval $search;          
$/ = "\n";

[download]
Don't use string eval, especially for something like that. That should be a single function call, see qr, quotemeta, local

In reply to Re^3: exe with wx gui - pp/wxpar issues by Anonymous Monk
in thread exe with wx gui - pp/wxpar issues by jhoop

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.