PHP 4.0 Bug #9265 Updated: passing preg_split a limit parameter of 0 supresses all matches

From: Date: Mon, 19 Feb 2001 19:31:14 +0000
Subject: PHP 4.0 Bug #9265 Updated: passing preg_split a limit parameter of 0 supresses all matches
Groups: php.dev 
Request: Send a blank email to php-dev+get-46949@lists.php.net to get a copy of this message
ID: 9265 Updated by: andrei Reported By: chuck@horde.org Old-Status: Open Status: Closed Bug Type: PCRE related Assigned To: Comments: As far as I remember, 0 has never meant "no limit" - the value for that is -1. But the documentation does need to be updated. Previous Comments: --------------------------------------------------------------------------- [2001-02-14 16:33:50] chuck@horde.org Somewhere in the last few weeks, preg_split changed so that specifiying a limit parameter of 0 returns the string to be split unchanged. Before that, 0 was seemingly treated as no limit, meaning that you could safely specify 0 as the limit argument in order to specify a flag as the fourth argument. <?php $foo = 'a|b|c|d'; $m = preg_split('/|/', $foo, 0); var_dump($m); ?> will return everything in the same array, whereas if the limit argument is left off (or increased), the string gets split up. The behavior allowing 0 to be no limit should be returned, or another safe argument for limit that means no limit documented. --------------------------------------------------------------------------- ATTENTION! Do NOT reply to this email! To reply, use the web interface found at http://bugs.php.net/?id=9265&edit=2

« previous php.dev (#46949) next »