Re: Bug in die_on_bad_params handling

From: "Sam Tregar" <[email protected]>
> That's a run-time error that happens during output() and the relevent file
and
> line numbers are currently only available during parse().

Sam, I'm curious: Why wouldn't my suggestion work? The croaked message
Matija referred to is in the param method. I can't find it anywhere else.
How does it reach the output method if it is croaking on this line as the
param is set?

After thinking about it: it seems like it would be easier for Matija to
provide all the vars in a tmpl_loop, passing empty strings (instead of
turning off "die_on_bad_params" and so H::T will fill ignore extra columns).
Or, maintain seperate loop names.

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