Re: Re: Any idea why we have two html_puts()'s?
| From: | Zeev Suraski | Date: | Sun, 12 May 2002 15:07:34 +0000 |
| Subject: | Re: Re: Any idea why we have two html_puts()'s? | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-83933@lists.php.net to get a copy of this message | ||
At 17:58 12/05/2002, Sascha Schumann wrote:
What inherent flaws? So far, the only difference between them that I could
spot was that php_html_puts() was buggy, and did not convert series of
spaces into 's. Otherwise, the only difference was the use of
buffering. I may have missed something, though.
That is not buggy, although it was not part of the original
php_html_puts. IIRC, Jani put it in place to prevent
excessivily wide tables in phpinfo(). I would not mind
adding an option for that though, if the original behaviour
is required for some purpose.
What I'm pointing out is that there are no 'inherent flaws' in the 'dog slow' implementation that we already had for a couple of years. If you want to add buffering, we can add buffering. There's no point in adding a specialized buffered implementation.
The spaces issue is well implemented in the zend implementation (I also fixed it in the php_html_puts() implementation, before I removed it; At some point, it was too much of a deja-vu, which is why I don't like duplicate implementations :)
Zeev