Thanks. Looks useful although in this case, the list is derived from a parameter supplied from a form and varies in length and content with each invocation, so I am not sure (I have the HTML::template tut onscreen now) that it is applicable to this use.

Regards.

HMTL::Template is very applicable for this. Here is a command line script that you can play with (i'll leave turning it into your CGI script as an exercise):

use strict;
use HTML::Template;

my $data = do {local $/; <DATA>};
my $temp = HTML::Template->new(
   scalarref => \$data,
);

$temp->param(
   row => [
      { 'link' => 'foo' },
      { 'link' => 'bar' },
      { 'link' => 'baz' },
      { 'link' => 'qux' },
   ],
);

print $temp->output;

__DATA__
<table border="1">
<tmpl_loop row>
<tr>
<td><a href="<tmpl_var link>"><tmpl_var link></a></td>
</tr>
</tmpl_loop>
</table>
[download]

I use the built-in DATA filehandle to avoid having to use a seperate template file, just save this code as foo.pl and run it.

jeffa

L-LL-L--L-LL-L--L-LL-L--
-R--R-RR-R--R-RR-R--R-RR
B--B--B--B--B--B--B--B--
H---H---H---H---H---H---
(the triplet paradiddle with high-hat)

Um...er.......Ok! *raised eyebrow*!

There is so much in this that I don't understand, I will need to play with it and read a lot before making useful comment, except to say that the values for the links are derived from the (single) passed parameter, rather than being directly extracted from them.

Its (currently) actually a relative path into the file system and the list is the list of subdirectories below the past relative path (specifically excluding ".." to prevent backing up passed the starting point; and taint will be used once I get around to understanding it!).

It will eventually (probably) be a key (pointer) into a hiarchical tree in a DB.