if( ! $ENV{PERL_PERTURB_KEYS} ) {
    $ENV{PERL_PERTURB_KEYS} = 1;
    $ENV{PERL_HASH_SEED} = ...;
    exec( $^X, $0, @ARGV );
    die "Failed to exec self: $!\n($^X $0 @ARGV)\n";
}

... rest of Perl code ...

[download]

You can add the BEGIN block if you want to optimize away some wasted initialization work.

Note that this does not take care of options being passed to Perl by the user, for example, if the script is being invoked like "perl -Imylib -i.old script *.ds". In a more likely scenario, you wouldn't be able to debug the script by just doing "perl -d script ...".

- tye        

In reply to Re^2: setting PERL_PERTURB_KEYS & PERL_HASH_SEED in a perl file (simpler) by tye
in thread setting PERL_PERTURB_KEYS & PERL_HASH_SEED in a perl file by gravid

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.