On Thu, Oct 22, 2009 at 9:56 AM, Bill Moseley <[email protected]> wrote:
> On Thu, Oct 22, 2009 at 9:50 AM, Sean McAfee <[email protected]> wrote: > >> Another useful thing might be to introduce a configuration option or two >> that provide more control over which warnings can be generated by evaluated >> template code, and how such warnings are disposed of. Something like: >> >> $t = Template->new({ >> WARNINGS => [ '+numeric', '-uninitialized' ], >> WARNSUB => \&aggregate_warnings, >> .... >> }); >> > > Isn't that the point of being able to localize $SIG{__WARN__} in your > application before calling $tt->process? > You're *not* able to do that. Template::Document localizes away whatever warning hook the main application might have installed. --Sean
_______________________________________________ templates mailing list [email protected] http://mail.template-toolkit.org/mailman/listinfo/templates
