#22226 [Opn->Bgs]: explode misbehaves exploding empty strings
| From: | iliaa@php.net | Date: | Sat, 15 Feb 2003 17:04:05 +0000 |
| Subject: | #22226 [Opn->Bgs]: explode misbehaves exploding empty strings | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-33239@lists.php.net to get a copy of this message | ||
ID: 22226
Updated by: iliaa@php.net
Reported By: php@savignano.de
-Status: Open
+Status: Bogus
Bug Type: Scripting Engine problem
Operating System: Win32
PHP Version: 4.2.1
New Comment:
Thank you for taking the time to write to us, but this is not
a bug. Please double-check the documentation available at
http://www.php.net/manual/ and the instructions on how to
report
a bug at http://bugs.php.net/how-to-report.php
If the separator string cannot be found the entire contents of the
passed string will be stored in the 1st element of the returned array.
This is intended behaviour.
Previous Comments:
------------------------------------------------------------------------
[2003-02-14 16:47:13] php@savignano.de
This was reported before (bug #8883) as
count(explode("|", "")) == 1
but was stated bogus for some unexplained reason.
The problem is: exploding an empty string returns an array with one
empty element, but should return an empty array instead.
I found this bug to be closed for PHP 3.0.3 (bug #699) with no comment,
but it seems it isn't fixed really?
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=22226&edit=1