> Exactly. The thing is trivial to read and understand Trivial, eh? Heh heh, well so trivial that you then present a null versus empty case... and dismiss it because it's probably "less common". ;-)
> May I introduce you to "intelligent" views: they tell you > when they were fed invalid data. The view isn't doing it... the Velocity Engine is making the call. That's my concern. > message (usually). I think if you had this problem, of the silently > vanishing lists that don't even appear as empty lists because HTML Hold on a bit, mate. I run into this all the time... I just solve it differently. > It's OK with tables, where you've got the header row even with 0 > results. But it's still much nicer to avoid writing out all the code, > several times, in every single template. Hmm... not sure of your point there, friend. But it does bring up another use case that this swank new #foreach/#else doesn't handle. Tables. #if ($SHOW_RESULTS) <TABLE> #foreach ($thingy in $results) $thingy #end </TABLE> #else No soup for you! #end Point is -- you need to put in the magic "do results exist" test outside the foreach... so your #else won't help you here, and you'll end up with dual logic anyway. <grin> > Only if you believe that every single VTL user should > re-invent the same wheel on every project - when it's a wheel that > - we all want the same algorithm for I agree we shouldn't invent the same things... but the trick is that we all must have the same, exact, identical wheel. Cheers, Timo --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
