Lines Matching refs:fragment
498 "Program fragment delivered error ``$err''";
662 # Prepend specified perl code to each fragment before evaluating:
772 C<{> begins a program fragment, which continues until the matching
800 Each program fragment should be a sequence of Perl statements, which
804 place of the program fragment itself.
823 fragment that begins on the third line, and the values of C<$diff> and
824 C<$more> set in the second fragment will persist and be interpolated
862 template. Also, if you use C<$OUT> in a program fragment, the normal
863 behavior, of replacing the fragment with its return value, is
864 disabled; instead the fragment is replaced with the value of C<$OUT>.
874 program fragment. It is private to C<Text::Template>, so
951 fragment, and the second string is the string that signals the end of
952 each program fragment. See L<"Alternative Delimiters">, below.
1234 value of the program fragment to begin with. For example, if the
1237 fragment that cased the error.
1242 Program fragment delivered error ``Illegal division by 0 at
1254 (3+4)*5 = Program fragment delivered error ``syntax error at template line 1''
1267 The source code of the program fragment that failed
1276 the failed program fragment.
1280 The line number of the template at which the program fragment began.
1392 of every program fragment. See L<C<PREPEND> feature and using
1399 beginning of each program fragment, and the second string is the
1400 string that signals the end of each program fragment. See
1592 to generate TeX output, the choice of braces as the program fragment
1612 absolutely must have a program fragment that mentions one of the
1637 undeclared variables and the like. But each code fragment is a
1639 each and every code fragment:
1654 Because we didn't put C<use strict> at the top of the second fragment,
1655 it was only active in the first fragment, and we didn't get any
1656 C<strict> checking in the second fragment. Then we misspelled C<$foo>
1661 added to the beginning of each program fragment.
1667 option; the statements will be prepended to each program fragment for
1685 The code in the second fragment would fail, because C<$boo> has not
1700 attach the perl statements to the beginning of each program fragment,
1724 The code in the second fragment would fail, because C<$boo> has not
1850 Remember that a program fragment is replaced with its own return