Well this is somewhat poor style, but you could say something like:

options => defined($hashref->{'options'}) || []
[download]

How about a nice map though that only pulls out the defined elements in your hash?

map { defined $hash->{$_} ? ($_ => $hash->{$_}) : ()  } keys %$hash;
[download]

The output then can be fed directly into param. This is limited too in that it assumes your hashkeys are identical to your fields (TMPL_VARS), but if you can live with that assumption it might work for you.

HTH

Thanks, the first solution works for me.

I didn't get the second solution to work. How do you get it work work given the code I gave about (the %hash and the generate subroutine).

Finally, how would you have set up a template like this?

Basically your generate subroutine would look like:

sub generate {
  my $hashref = shift;
  my $template = HTML::Template->new(filename => "$tmpldir/generic.tt"
+);
  $template->param(map { defined $hashref->{$_} ? ($_ => $hashref->{$_
+}) : ()  } 
          keys %$hashref);

   );
   print $template->output;
}
[download]

This works because HTML::Template::param expects a list an even number of elements in length suitable for hash type operations, and map of course produces lists, so our expression there utilizes the ternary operator (?:) to test for defined values and outputs key/value pairs.

I am not really qualified to give advice about template design since I'm new to it myself. But just the fact you're using them I can comfortably say is a good sign :)

---

"The dead do not recognize context" -- Kai, Lexx