First off, get in the habbit of making backups. "Misplacing" files isn't a good idea, as I'm sure you're finding out.

The B::Deparse may be worth while investigating, I'd still say your time would be better spent implementing a working backup routine, rather relying on getting some form of your source code back via this method.

If PerlApp works in a reasonably similar manner than other Perl packagers I'm sure you'll be able to get at least an obfuscated version of your source code back from packaged versions. See decompile perlapp 4.1 or Super Search for similar posts.

In reply to Re: Print perl source code in compiled script... by marto
in thread Print perl source code in compiled script... by bcarroll

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.