Is this an undocumented PHP 4.3.6 bug?

ppowell

   echo "val = $val<P>";
   list($mySection, $myDisplay) = explode('|', $val);
   echo "mySection = $mySection and myDisplay = $myDisplay<P>";

In using PHP 4.3.6 here are my results:

val = image|Image Maintenance

mySection = image and myDisplay = image

I narrowed down the problem to this:

$blahArray = explode('|', $val);
print_r($blahArray);
$blahArray = split('|', $val);
print_r($blahArray);

Nothing prints out, the array $blahArray is never set, not even to an empty array. No error messages nor warnings result in this.

Has anyone had any similar problems with PHP 4.3.6 or am I just the "lucky one"? If so, is this an undocumented bug in 4.3.6 (all I could find in www.php.net was that there was a negative limit to explode() ).

Phil

LordShryku

I'd say you're the lucky one. Try setting $val as a static variable and testing. Here's what I did and it worked good.

[root@cux012wms inspection]# php -v
PHP 4.3.6 (cli) (built: Apr 19 2004 14:39:56)
Copyright (c) 1997-2004 The PHP Group
Zend Engine v1.3.0, Copyright (c) 1998-2004 Zend Technologies
    with the ionCube PHP Accelerator v1.3.3r2, Copyright (c) 2001-2002, by Nick Lindridge
[root@cux012wms inspection]# vi test.php
[root@cux012wms inspection]# php test.php
val = image|Image Maintenance <P>mySection = image and myDisplay = Image Maintenance <P>
[root@cux012wms inspection]#

# contents of test.php
<?php
$val = "image|Image Maintenance ";
echo "val = $val<P>";
list($mySection, $myDisplay) = explode('|', $val);
echo "mySection = $mySection and myDisplay = $myDisplay<P>";
?>

ppowell

Ok apparently it is not PHP itself (though then again just for giggles sake we bounced Apache), but now I have no idea why it's happening so I'm having to debug with print_r() tracers all over the place, will update you guys later.

Phil

LATER:

I traced the problem to this function:

	function &getCount($result) {
		return @sizeof($result);
	}

Where $result is an array of objects. Though $this->getCount() returns a value, it also sets an unset variable elsewhere called $val to 0. I have absolutely no explanation for this, but this same error is occurring in another script as well where $hasResult inexplicably gets the value of $imageURL.

Phil