On Fri, 27 Jun 2003, Adam Gent wrote:
> We are trying to use one of the H::T options search_path_on_include
>
> But we can not seem to get it to work.
What do you think it does? You didn't mention anywhere
in your example which makes me think you might not understand the
feature...
> We are u
Hi,
We are trying to use one of the H::T options search_path_on_include
But we can not seem to get it to work.
We are using the following
my $t = HTML::Template->new(
filename => 'appgenform.tmpl',
global_vars => 1,
cache => 1,
search_path_on_include => 1,
In article <[EMAIL PROTECTED]>, Andrew Brosnan wrote:
> In the docs, regarding nested loops it says:
>
> $template->param(LOOP => [{ name => 'Bobby',
>nicknames => [{ name => 'the big bad wolf' },
> { name => 'He-Man' },
>
Chisel Wright [EMAIL PROTECTED] wrote:
> I've always been uncomfortable using eval().
> I know /how/ to use it, but it just feels dirty.
> What are the negative effects (if any) of using eval()?
Fundamentally here are two different ways of using eval (plus, of
course, the option of not using it a
Hello, a suggestion:
Wrap your calls in 'load_tmpl( )' and then do
my $ht = $self->load_tmpl(...)
or my_error_handling_routine(...);
Use the eval call in load_tmpl( ) to determine if you return false or
true.
Just the way I would do it ...
Sincerely,
Cory Trese
Lead Web Application D
On Fri, Jun 27, 2003 at 04:52:23AM -0400, Chris Reinhardt wrote:
> eval { ...code that dies... };
> if ($@) {
> # There was an error in the eval {}
> }
I've always been uncomfortable using eval().
I know /how/ to use it, but it just feels dirty.
What are the negative effects (if any) of usi
On Fri, 27 Jun 2003, Vince Veggus wrote:
> Is there a way to catch the "die" that carp::croak calls?
perldoc -f eval
perldoc -f die
--
"I think trash is the most important manifestation of culture we have in my
lifetime."
- Johnny Legend
--
Hello Chris,
thanks - works fine!
Best regards,
Vincemailto:[EMAIL PROTECTED]
-
Friday, June 27, 2003, 10:52:23 AM, you wrote:
CR> [snip]
>> Is there a way to catch the "die" that carp::croak calls?
CR> eval { ...code that dies... };
CR> if ($@) {
CR>
On Fri, 27 Jun 2003, Vince Veggus wrote:
[snip]
> Is there a way to catch the "die" that carp::croak calls?
eval { ...code that dies... };
if ($@) {
# There was an error in the eval {}
}
--
Chris Reinhardt
[EMAIL PROTECTED]
Systems Architect
Dynamic DNS Network Services
http://www.dyn
Hello all,
this is not an exclusive html-template question but html-template uses
carp::croak() too...
A module similar to H::T croaks and therefore the script using this
module ist stopped to immediately. A Message goes to stdoud and the
script stops. I am unable to start my own error routines w
10 matches
Mail list logo
