Re[4]: Incorrect newline counters
Dmitry Koteroff <[email protected]>
| Newsgroups | gmane.comp.php.smarty.devel |
|---|---|
| Message-ID | <[email protected]> |
B> What's the problem here anyhow? I'm not against getting this
B> "fixed", but what is broken? Is anyone complaining about the
B> current behaviour?
Aha.
-------------
xxx
{if $foo}
bar
{/if}
yyy
-------------
Result:
-------------
xxx
bar
yyy
-------------
Suddenness.
B> Dmitry, for the several half-hours you spent building your
B> patch, as has been said many times, many many hours of many
B> people's time went into getting the current behaviour as it
B> is. Not to mention the issues surrounding the associated strip
B> behaviour.
I understand.
B> You may as well go into php-dev and tell them that you have a
B> simple patch for "correcting" PHP's case insensitivity
B> problem. It's not that you are wrong, its that people don't
B> care and moreso, they don't want the change.
Most of people people want generally nothing (except of whiskey
or vodka, of course). But it is not a cause not to accomplish
Smarty.
B> So here's the deal, if your patch is accepted in any form,
B> will you personally gaurantee to verify and correct all of my
B> templates (and whoever else asks) whose output may change as a
B> result of this?
We will not need to correct any template at all.
What do you say about the example above? Do you use its
side-effect in your templates? Doubtful.
B> So unless you can present a series of well defined test-cases that show
B> how your changes will have absolutely, gauranteed, no effect on the
B> output, I can't see anyone supporting your changes.
I'll do it, and I am ready to improve Smarty "space behavour" at
all (together with line number synchronization), but I need
sanctions.
--
Best regards,
Dmitry Koteroff.
--
Smarty Development Mailing List (http://smarty.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php