Lines Matching refs:will
676 # All templates will always have `use strict vars' attached to all fragments
787 If you have an unmatched brace, C<Text::Template> will return a
802 executed will be evaluated in scalar context; the result of this
807 fragments will persist into later fragments:
822 The value of C<$x> set in the first line will persist into the next
824 C<$more> set in the second fragment will persist and be interpolated
825 into the last line. The output will look something like this:
861 Anything you append to this variable will appear in the output of the
883 that does not exist, C<$Text::Template::ERROR> will contain something like:
893 template object. C<SOURCE> says where the template source code will
923 C<Text::Template> will read the text from the filehandle up to
931 C<SOURCE> is required. If you omit it, the program will abort.
957 C<SOURCE> is a C<FILE>, then the data will be decoded from the given encoding
970 considered 'untrustworthy', and taint mode will not allow you to
976 C<UNTAINT =E<gt> 1> in the call to C<new>. This will tell
979 trustworthy. It will also disable taint checks on template code that
1053 omit the C<PACKAGE> option, C<$x> will be replaced with the value of
1057 template makes changes to variables, those changes will be propagated
1060 in your program if it wants to, but it will have to do so explicitly.
1079 We want to pass in an array which will be assigned to the array
1097 But if you use the C<PACKAGE> option, you will probably be safe even
1103 In this case the template will clobber the variable C<$Q::item_no>,
1127 will fill out the template and use C<"The King"> as the value of
1181 If you do this, the template will have a variable C<$database_handle>
1183 template will have a hash C<%database_handle>, which exposes the
1194 calls to C<fill_in> that use the same package will pick up the values
1222 C<Text::Template> will invoke the function. This function is called
1223 the I<C<BROKEN> function>. The C<BROKEN> function will tell
1226 If the C<BROKEN> function returns C<undef>, C<Text::Template> will
1232 If the C<BROKEN> function returns any other value, that value will be
1235 C<BROKEN> function returns an error string, the error string will be
1260 C<fill_in> will pass a hash to the C<broken> function.
1261 The hash will have at least these three members:
1317 If one of the program fragments in the template fails, it will call
1329 example, and pass C<foo.txt> as the C<FILENAME> parameter, errors will look
1343 will die with an error that contains
1351 program fragments will be performed in this compartment. See L<Safe>
1356 will be placed into the safe compartment and evaluation will take
1366 without C<PACKAGE>, the hash variables will just be loaded into the
1376 The generated text will be printed to this filehandle as it is
1433 Pay or I will break your {$part}.
1480 It will be a lot faster because it only has to read and parse the file
1556 worry that evaluation of the little programs will creep out into the
1585 actually how C<$OUT> works.) I can fix this, but it will make the
1587 about this, send me mail and I will show you what to do about it.
1667 option; the statements will be prepended to each program fragment for
1692 in which case the statements will be prepended each time you fill in
1699 If you do this, then call calls to C<fill_in> for I<any> template will
1728 C<HASH> option will be an error.
1757 objects in class C<Derived> I<will> be affected by
1783 will ensue when perl tries to evaluate these as if they were Perl
1871 instead. Presumably, C<$SILENTLY> has no value, so nothing will be
1884 happened to use a variable named C<$OUT>, you will have to change them
1885 to use some other variable or all sorts of strangeness will result.
2006 text - the text that will be appended
2329 The line number information will be wrong if the template's lines are
2331 problem. If you do, I will fix it.