Re: Re[2]: Incorrect newline counters

--- Dmitry Koteroff <[email protected]> wrote:
> MO> I  think  (someone  correct  me  if  this isn't right) custom
> MO> functions must produce their own newlines if they need them.
> I'll correct. (-;
> 
> How would they know if they need to emit \n?
> 
> How  would  user-defined  function  know if it is situated in the
> middle of the line or at the end of line?
> 
> I see only two ways to solve the problem:
> 1. pass each function additional parameter (it's too bad), and
> 2. move \n insertion from compile-time to runtime.
> 
> Seems there are no other solutions.

What's the problem here anyhow? I'm not against getting this "fixed",
but what is broken? Is anyone complaining about the current behaviour?

Dmitry, for the several half-hours you spent building your patch, as
has been said many times, many many hours of many people's time went
into getting the current behaviour as it is. Not to mention the issues
surrounding the associated strip behaviour.

You may as well go into php-dev and tell them that you have a simple
patch for "correcting" PHP's case insensitivity problem. It's not that
you are wrong, its that people don't care and moreso, they don't want
the change.

So here's the deal, if your patch is accepted in any form, will you
personally gaurantee to verify and correct all of my templates (and
whoever else asks) whose output may change as a result of this?

So unless you can present a series of well defined test-cases that show
how your changes will have absolutely, gauranteed, no effect on the
output, I can't see anyone supporting your changes.

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