Christoph said:
> Nathan Bubna wrote:
> >[snip]
> > thus, i'd also be fine with having 1.5 *eliminate all* whitespace
gobbling
> > by default (with filters optional)
> >[snip]
> >In another mail in this thread Nathan Bubna wrote:
> >[snip]
> > personally, i think it's a "flaw" to gobble any whitespace outside of
> > directives or method calls on a variable (a.k.a. whitespace in the
schmoo
> > stays untouched). :-) it may not be optimal for having both pretty
output
> > and pretty code, but it is by far the most intuitive way to go. no
complex
> > or debatable rules to be figured out, just a simple "what you type
(non-VTL)
> > is what you get" policy.
>
> +1
> Only thing to add here is: where do you set the limits of VTL. I proposed
in
> the past to see standalone VTL (directives that have only whitespaces
around
> them) to include the surrounding whitespaces. This means, that if I markup
> existing (text) schmoo I just need to add new VTL lines and all schmoo
remains
> untouched. Or I insert VTL within a schmoo line and again all remains the
same...
i don't think we agree on this one. i definitely don't consider whitespace
surrounding VTL to be part of the VTL. when you say "standalone VTL," you
mean VTL that is alone *on its line.* I don't mean that. In the below
example, the spaces with ^ under them are schmoo (according to me).
#if ( $blah )
^^^^ ^^
you see, your proposal is not at all like mine. i am proposing the
elimination of whitespace gobbling by default. you are proposing more
whitespace gobbling. (i.e. that all directives gobble in the manner #set()
currently does).
that said, i would still prefer yours (a more sensible gobbling scheme) to
the current state of things. i just think it'd be better to eliminate
schmoo gobbling period.
anyway, let's not drag this out. we've been over these things a dozen
times, and we still have releases 1.3.1, 1.3.2, and 1.4 that need to happen
first. once that's done, and 1.5-dev is cooking, we can put these proposals
out there and let the voting, arguing, and chest-pounding be done.
> > this is tied to my opinion that all whitespace ought to be treated
equally
> > with the obvious exception of the line break closing a single line
comment,
> > thus allowing multi-line directives, method calls, etc.
>
> +1 ... if the VTL boundary issue is also clear ...
clear as mud. :-)
Nathan Bubna
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
