From: "Sam Tregar" <[EMAIL PROTECTED]> > The loop output code calls param() to setup each row.
I see it now. The output method calls the package HTML::Template::LOOP which calls param(). It would take some work to 1) collect (in a hash) die_on_bad_param flags when the user calls param() with an array (or arrays). And then 2) use that hash to set the global value from inside HTML::Template::LOOP prior to calling param(). The overhead involved in doing that starts to diminish the cost of using the same table structure and pass empty strings when not needed. Or, using a TMPL_IF (as Roger suggested). Also, if the data associated with two loops is so large that it's costly to create a data structure for each one, that seems to indicate it should be displayed in two pages. To the extent it's difficult for the computer, I'd think it's at least that difficult for whoever's on the receiving end. :) Thanks, Mark ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ Html-template-users mailing list Html-template-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/html-template-users
