> if you have a "very unique wheel" - don't use the feature! > The fact that > the feature isn't useful in every single usecase is hardly > reason to drop it
I'm not saying drop it, if somebody else codes it, that's fine... I'll only cringe if/when a template designer uses it. ;-) I'm over here on the unfashionable end of the discussion pointing out use cases where #empty doesn't seem all that useful. I come up with them, but others keep saying, "Well, yeah...but it'd still be oh so useful for 'everybody' else." <grin> By my count, I've got more use cases where it doesn't work than ones where it does. Lol. Shall I keep coming up with cases? :-) Over the years there are folks who use Velocity for a few weeks and pop on the list to say "This is GREAT STUFF!... but... it'd be awesome if it had Feature X! Somebody should code Feature X and then Velocity would be PERFECT [for me]!" Then there are folks who say, "well... it works fairly well already, and we'd like to keep the core simple and small, can't you do this with a macro or tool? Oh, you can. Great. Moving on..." *** Me -- I'm just in that latter camp. Call me crufty. :-P Timo *** Humourously: At that point, the User forks their own project, creates Feature X and all of the Velocity user base flocks to their new insanely cool template engine... or not. <grin> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
