Herein some comments on various recent ideas, with my 2 cents.
I'm in favor of gobbling/ignoring all whitespace inside #directives - to allow for: > > #set( $array = > > "foo", > > "bar", > > "woogie" ) > > #myVM( 'one' > > $two ) > $foo.method( $bar.woogie > $bar.boo ) --- > > > as for the breakage the \c -> c change would cause... Wouldn't that break all of those Windoze pathnames in templates? D:\foo\bar\hate\this\slash\thingy And require template folks to turn them into: D:\\foo\\bar\\hate\\this\\doubleslash\\thingy\\even\\more Ugh. ;-) --- Right now, #set won't allow multi-lines (correct?) which means that it violates the new idea that "if the template owner typed it, they must want it". Also means I'd need \n \t \s \\ etc. etc. in order to add them to a string. If multi-lines where allowed, then I don't see a need for the escaped chars (excepting #set ($foo = "this is my \"quote\" of the day") for which we already have a workaround with #set ($quote = '"')... which is remarkably similar to the way HTML escaped entities specify a quote explicitly -- " - http://www.w3.org/TR/REC-html40/sgml/entities.html) FYI: I'm not in favor of new directives (ex. #setinline, #collect, etc.). "<<HERE" constructs should be left in the Perl world. #set( $foo = "foo bar" ) The "don't gobble" rule could be followed, and newlines in the string are there by simply typing them... but alas, what about templates edited on a Mac versus a PC versus a Linux box? (CR / CF+LF / LF) ? That is, what happens? What's $foo got in it? Timo P.S. Don't say I didn't speak up. ;-) -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
