If he didn't post something to that effect then I would have done it myself. It's not that this problem is below us, it's that it is a very simple problem to solve. Another thing is that your code was thrown together without any test runs. How do I know?

Global symbol "@file" requires explicit package name at prob58.pl line + 6. Global symbol "%file" requires explicit package name at prob58.pl line + 7. syntax error at prob58.pl line 7, near "$file {" Global symbol "$file" requires explicit package name at prob58.pl line + 8. Global symbol "@account" requires explicit package name at prob58.pl l +ine 9. Global symbol "%account" requires explicit package name at prob58.pl l +ine 11. syntax error at prob58.pl line 11, near "$account {" Global symbol "$fullname" requires explicit package name at prob58.pl +line 12. Global symbol "$username" requires explicit package name at prob58.pl +line 12. Global symbol "$mothers" requires explicit package name at prob58.pl l +ine 12. Global symbol "$email" requires explicit package name at prob58.pl lin +e 12. Global symbol "$referral" requires explicit package name at prob58.pl +line 12. Global symbol "$ip" requires explicit package name at prob58.pl line 1 +2. Global symbol "$account" requires explicit package name at prob58.pl l +ine 12. Global symbol "$fullname" requires explicit package name at prob58.pl +line 14. Global symbol "$username" requires explicit package name at prob58.pl +line 14. Global symbol "$mothers" requires explicit package name at prob58.pl l +ine 14. Global symbol "$email" requires explicit package name at prob58.pl lin +e 14. Global symbol "$referral" requires explicit package name at prob58.pl +line 14. Global symbol "$ip" requires explicit package name at prob58.pl line 1 +4. syntax error at prob58.pl line 16, near "}" prob58.pl has too many errors.

Turn off strict, still no go:

syntax error at prob58.pl line 7, near "$file {" syntax error at prob58.pl line 11, near "$account {" syntax error at prob58.pl line 16, near "}" Execution of prob58.pl aborted due to compilation errors.

The problems with your code are as follows:

I don't know about the other monks, but I am offended when someone asks me for help and then throws what could at best be described as perl-esque pseudocode. Seek help for the wisdom, don't seek help for the answer.

antirice    
The first rule of Perl club is - use Perl
The
ith rule of Perl club is - follow rule i - 1 for i > 1


In reply to Re: Re: Re: Opening Unknown Filenames by antirice
in thread Opening Unknown Filenames by Anonymous Monk

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.