it's pretty good. but my brain parses it as "forn one" instead of "fornone". oh, and the #forone is redundant IMHO and would presumably change the behavior of the #foreach() section. i don't like that.
anyway, if we're gonna vote (wiki?) about this vaporware, i'd stick with #else first or go with Gonzalo's #otherwise. :) i really don't see a problem with #else as long as the docs are clear on the render/no-render paradigm. regardless of whether the initial condition is a boolean evaluation or rendering decision, the word/directive "else" (or its synonym "otherwise") rather clearly implies the presence of a default alternate. i don't find anything confusing about that. On Mon, 10 Jan 2005 15:38:28 -0800, Will Glass-Husain <[EMAIL PROTECTED]> wrote: > I kind of like this. Seems the clearest syntax of any proposed. > > WILL > > > ----- Original Message ----- > From: "Chris Rousseau" <[EMAIL PROTECTED]> > To: "Velocity Developers List" <[email protected]> > Sent: Monday, January 10, 2005 8:18 AM > Subject: RE: Just a thought...foreach else ? > > What about: > > #foreach() > ... > #fornone > ... > [#forone] > ... > #end > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
