Thanks, interesting module, I will learn a lot.¹

(I think I subconsciously had this in mind =)

But it doesn't seem to address the hygiene problem.

As an illustration by extending the synopsis (untested)


sub wrap {
  my ($old_body, $environment) = @_;


  my $new_body = <<'__WRAP__';

    #---PRE_BODY
    my $foo++;      # new var

    #<OLD_BODY>#

    #--- POST_BODY
    print $foo;

__WRAP__

  $new_body =~ s/#<OLD_BODY>#/$old_body/g;


  my $code = eval_closure(
      source      => "sub { $new_body }",
      environment => $environment,
  );

}

[download]

Now the problem starts if $foo is part of the closure environment.

I tried to solve this by using placeholders like $<FOO> in the wrapped code.

This translates (regex) to $_FOO_ iff $_FOO_ is not already part of the environment.

Otherwise it translates to something like $_FOO_A .

(the suffix is incremented till there is no conflict)

Other strategies (gensym, obfuscation, packages) are listed in the WP article, but I wanted to have a notation with readable symbols in the debugger.

I hope it's clearer now.

Cheers Rolf

(addicted to the Perl Programming Language and ☆☆☆☆ :)

¹) especially how the use of PadWalker was avoided?

In reply to Re^2: Hygienic eval of templates with perl code? by LanX
in thread Hygienic eval of templates with perl code? by LanX

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.