>>> Thus i suggesst we reintroduce the patch and live with the fact >>>that we need to write echo "<"."/script>" instead of echo "</script>".
If that was said some 5 years ago, it would be somewhat reasonable (though I would probably have some doubts even then, but it would be at least arguable). But now when I see this patch breaks live site in a way that takes me half an hour just to find it out - and that's while I KNOW about the patch and it's effects and can figure out what the hell is going on - try to imagine what would the average developer say. One that does not follow each patch on internals list. He would just refuse to upgrade to this version on grounds that "it breaks my site that worked before" and he'll be right. So what's the use in a "fix" that nobody would use - just to show how purist we are? Or do you imagine all the users would suddently See The Light (TM) and go and rewrite all their scripts? It won't happen. Nobody would rewrite working code just because someone thinks it's not nice for some obscured XML-purity reasons. -- Stanislav Malyshev, Zend Products Engineer [EMAIL PROTECTED] http://www.zend.com/ +972-3-6139665 ext.115 -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
