Re: [PHP4BETA] urldecode diff php3<->php4
| From: | Zeev Suraski | Date: | Tue, 22 Jun 1999 20:25:32 +0000 |
| Subject: | Re: [PHP4BETA] urldecode diff php3<->php4 | ||
| References: | 1 | Groups: | php.version4 |
| Request: | Send a blank email to php-version4+get-1659@lists.php.net to get a copy of this message | ||
At 21:16 22/06/99 , Thies C. Arntzen wrote:
On Tue, 22 Jun 1999, Zeev Suraski wrote: At 15:33 22/06/99 , Thies C. Arntzen wrote:Exactly. I misread your letter obviously, I thought you were suggesting to change RETURN_FALSE to return "" instead of false :) Zeev -- Zeev Suraski <zeev@zend.com> http://www.zend.com/ For a PGP public key, finger bourbon@netvision.net.ilhmm, not quite sure with this one: script: <?php $data = urldecode(""); var_dump($data); ?> result with php4: Content-Type: text/html i:0 result with php3: Content-type: text/html string(0) "" i just got "badly" bitten by this one! i think we should change the RETURN_FASLE in encode/decode to return an empty string 'cause urldecode("") in deed is "" - and not FALSE - any objections??Yes - I object. RETURN_FALSE should return false. We have a boolean type now. hmm, some misunderstanding here (from my side) - do we agree that urldecode("") returns (from now on) "" (empty_string) instead of FALSE? "" still evaluates a false, but functions like urlencode should only return false if something bad happened, right?