(resending to get onto the new thread) Christoph wrote: > having a completely whitespace-gobbling-free handling is a > clean as you can get; +1
> but it is not what most people expect. Hmm... Personally, I am continually confused by the -current- gobble rules because if I type it, I expect to see it in the output. Cold Fusion, for example, gobbles nothing. Granted, a faq was "Why did extra whitespace appear after a 1000 iteration loop?". But it is simple to explain, "CF ouputs EVERY char. Period." That is far easier to grok than, "Velocity's behaviour is to gobble up *excess* whitespace." (http://jakarta.apache.org/velocity/user-guide.html#VTL:%20Formatting%20 Issues) Where the definition of 'excess' is a benighted, confusing, and vehemently argued subject by many. ;-) > So it might be good to cleanup the parser to not gobble > anything, but have some pluggable AST-post-processors to do > the desired trimming - in addition to the filter directive. +1 since most existing Velocity folks do expect some benighted gobbling. Christoph wrote: > The whitespace handling I proposed would be the most wanted > form, IMHO. LOL ;-) -Timo --------------------------------------------------------------------- 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]
