Lines Matching refs:with
14 # ABSTRACT: Expand template text with embedded Perl
91 # sharing the expression with them. We install $source separately
610 Text::Template - Expand template text with embedded Perl
631 $text = $template->fill_in(); # Replaces `{$recipient}' with `King'
652 # Evaluate program fragments in Safe compartment with restricted permissions
658 # Parse template with different template file syntax:
685 them with their values.
750 they build it so that a string like C<%%VAR%%> is replaced with the
762 code in your template, with C<{> at the beginning and C<}> at the end.
774 fragments are evaluated, and each one is replaced with the resulting
797 I<not> done when you specify alternative delimiters with the
839 list with a header, like this:
847 One way to do it is with a template like this:
863 behavior, of replacing the fragment with its return value, is
864 disabled; instead the fragment is replaced with the value of C<$OUT>.
901 opened with the Perl C<open> command, so it can be a pipe or anything
902 else that makes sense with C<open>.
942 Pick a style you like and stick with it.
972 person might have tampered with the file.)
980 comes from a filehandle. When used with C<TYPE =E<gt> 'string'> or C<TYPE
986 for help with this feature.
1031 Pick a style you like and stick with it. The all-lowercase versions
1052 the template is actually replaced with the value of C<$R::x>. If you
1053 omit the C<PACKAGE> option, C<$x> will be replaced with the value of
1094 template by declaring it with C<my>. If the template does this, you
1098 if the template does I<not> declare its variables with C<my>:
1107 declared with C<my>, unless you give the template references to those
1207 You can also use this to set two variables with the same name:
1234 value of the program fragment to begin with. For example, if the
1332 Note that this does NOT have anything to do with loading a template from the
1343 will die with an error that contains
1355 If you use the C<PACKAGE> option with C<SAFE>, the package you specify
1404 any delimiters you set when you created the template object with
1439 `here document' with the C<E<lt>E<lt>> notation.
1505 This imports the C<_load_text> function into package C<Q> with the
1506 name C<include>. From then on, any template that you fill in with
1547 or pass the names and values in a hash with the C<HASH> option:
1553 All variables are evaluated in the package you specify with the
1559 Nevertheless, there's really no way (except with C<Safe>) to protect
1582 variables all have names that begin with C<$fi_>, so if you stay away
1584 you can tamper with them deliberately for exciting effects; this is
1598 an alternative set of delimiters with the C<DELIMITERS> option. For
1609 choose delimiters that do not conflict with what you are doing. The
1626 It may be safer to choose delimiters that begin with a newline
1691 template object with C<new>, you can also supply a C<PREPEND> option,
1850 Remember that a program fragment is replaced with its own return
1876 Every effort has been made to make this module compatible with older
1889 processor always replaced it with a single backslash before passing
1913 contexts, they are special; C<\\> is replaced with C<\>, and C<\{> and
1943 Starting with C<Text::Template> version 1.20, backslash processing is
2002 method. It is passed a list of pairs with these entries:
2326 by template evaluation. They all begin with C<fi_>, so avoid those