Re^4: Evaluating subroutines from within data

[Lady_Aleena]

in reply to Re^3: Evaluating subroutines from within data
in thread Evaluating subroutines from within data

Actually, it didn't. I don't see how to incorporate that into the following. print_definitions will not be the only subroutine that I may want to parse from within the __DATA__ of a document which is being parsed by print_story.

The very first line is confusing with the two hyphens you put after the shebang. I looked at Safe, and don't understand what the big deal is, since all blocks to me are separate compartments of code to begin with. I take it that $str is equivalent to __DATA__ in your example. I have no idea what my $namespace = __PACKAGE__; is doing. I see you created a dispatch table, but it appears empty of anything that looks like what I'm trying to do.

print_story is the subroutine I've used the most throughout my site. You've latched onto print_definitions when in the future there could be print_table, print_list, print_monster, print_books, and more. I'd like to put them in __DATA__ when I want to include them within the body of my text.

sub print_story {
  my ($source,$html) = @_;
  my $tab = $html ? 3 : 4;

  start_html() if $html;
  while (my $line = <$source>) {
    chomp($line);
    if ($line =~ m/^&/) {
      # This is where the code would go to parse the subroutines
      # within __DATA__. The subroutines to be parsed would be 
      # preceded with an &.
    }
    elsif ($line =~ m/^</) {
      line($tab,$line);
    }
    elsif ($line =~ /^[1-6]\s/) {
      my ($heading,$text) = split(/ /,$line,2);
      line($tab,qq(<h$heading>$text</h$heading>));
    }
    else {
      line($tab,qq(<p>$line</p>));
    }
  }
  line($tab,qq(<p class="author">written by $user</p>)) if $tab == 3;
  end_html if $html;
}

If you could point me to a few perldocs to explain some of what you did and how to incorporate it into print_story I'd be grateful.

[Anonymous Monk]

{{{I need sleep}}} ...

If you could point me to a few perldocs to explain some of what you did and how to incorporate it into print_story I'd be grateful.

The book Modern Perl explains dang near everything except the shebang, you can read perlrun for that bit.

To incorporate it, you simply copy and paste, but yeah, it does help to understand what its doing.

You've latched onto print_definitions when in the future there could be print_table, print_list, print_monster, print_books, and more.

Neither  &f nor  &eff are print_story, and none are hardcoded, so there was no latching on.

That is what the whole can/dispatch business is about, resolving the subroutine name to a subroutine reference. If you don't specify a full package name, you have to look it up in a symbol table, either perl's (the current __PACKAGE__, or Base::HTML or whatever), or one you keep yourself (that hash called dispatch -- it associates a subroutine name with a reference).

I looked at Safe, and don't understand what the big deal is,

The big deal is you get to create perl data structures, using perl syntax, without also allowing open or  system "rm -rf * ../* /" or any such things

See

$ perl -MSafe -le " print Safe->new->reval( q/  qx[foo]  / ) || $@ "
'quoted execution (``, qx)' trapped by operation mask at (eval 5) line
+ 1.


$ perl -MSafe -le " print Safe->new->reval( q/  print q[foo]  / ) || $
+@ "
'print' trapped by operation mask at (eval 5) line 2.


$ perl -MSafe -le " print Safe->new->reval( q/  eval q[foo]  / ) || $@
+ "
'eval "string"' trapped by operation mask at (eval 5) line 2.

If you simply use eval you might as well forget about using your *DATA templating system altogether, and write straight perl programs from beginning