[prev in list] [next in list] [prev in thread] [next in thread] 

List:       smarty-dev
Subject:    Re: Re[6]: [SMARTY-DEV] Incorrect newline counters
From:       boots <jayboots () yahoo ! com>
Date:       2004-06-02 15:00:22
Message-ID: 20040602150022.43675.qmail () web50806 ! mail ! yahoo ! com
[Download RAW message or body]

--- Dmitry Koteroff <delete@koteroff.ru> wrote:
B> Yes, this is a known behaviour that is suboptimal. What do you
B> expect  I  have  done  to-date?

DK> I  expect  nothing,  of  course. On the contrary - I offer to fix
DK> this by myself (later or soon), modifying and automatizing method
DK> which is used to generate compiled code (tags must not care about
DK> \n's and line sync at all, newlines are not their business).

Of course my question was rhetorical as I answered it myself (but you
cut that part out)--I workaround this issue. That's why I continutally
quote "fix" in this regard; it isn't a "fix" if it breaks working code,
but rather is a change. A subtle but important difference, IMO. If
there was a published spec that Smarty was breaking, that is one thing;
unfortunately, this was never formalized--but at least it's behaviour
was understood to lesser and greater degrees ;-)

B> Well,  in principle, that is a good thing. All I really ask is
B> that  you present your changes in a way that clearly shows how
B> the  behaviour  will  be  modified  (or prove that it won't be
B> changed).

DK> Proposals of new behavour (eating leading whitespaces) are here:
DK> http://news.php.net/article.php?group=php.smarty.dev&article=2371

Yes, that is one of the posts I am refering to :)

B> It appears that there is now some discussion and documentation
B> occuring  around  that  point  and that is far more acceptable
B> than a patch to a sensitive area that merely purports to be an
B> improvement  without  providing  even  test  cases let alone a
B> thorough examination of the issues.

DK> We  should  reach  agreement  first about whitespace concept, and
DK> only after that write test cases.

Conversely, the current behaviour must be documented, otherwise it will
be hard to explain what changes one will need to make to their existing
codes.

Instead of taking all of this on yourself, what would help you get
these goals accomplished?

cheers!
xo boots


	
		
__________________________________
Do you Yahoo!?
Friends.  Fun.  Try the all-new Yahoo! Messenger.
http://messenger.yahoo.com/ 

-- 
Smarty Development Mailing List (http://smarty.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

[prev in list] [next in list] [prev in thread] [next in thread]