php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Doc Bug #11937 Clarification of $foo = new Class and $foo = &new Class
Submitted: 2001-07-06 14:52 UTC Modified: 2001-12-12 17:09 UTC
From: phil3k at aon dot at Assigned:
Status: Closed Package: Documentation problem
PHP Version: 4.0 Latest CVS (2001-06-27) OS: Any
Private report: No CVE-ID: None
 [2001-07-06 14:52 UTC] phil3k at aon dot at
<?php
	
    //Two elements in an Array
    $array[] = "Maria";
    $array[] = "Lisa";
	
    //just a test output
    array_walk ($array, "my_print");


    //and then free the first element of the array
    unset ($array[0]);

    function my_print ($value)
    {
	print $value . " ";
    }
	
    print "<br />";
    //The following dump will produce:
    //array(1) { [1]=> string(4) "Lisa" } 
    //This means that the first element has the index 1 
    //But it should have index 0
    var_dump ($array);
?>

If you have more than two elements, and you free one of them, you can just prevent this bug, by resorting the array with any sort function. But with only two elements, this won't work, and if you clear the first of these, you will get the same result as I have got, there was one element,  but with the wrong index.

Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2001-07-06 15:20 UTC] vlad@php.net
If you unset an element in the array, it does not make the whole array shift so it starts from index zero again. That's normal behaviour.
 [2001-07-07 09:10 UTC] jeroen@php.net
Should be more clear in the docs. It is only implicitely there.

Assigning to myself.
 [2001-12-12 17:09 UTC] jan@php.net
fixed in CVS. 
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Wed Apr 24 03:01:29 2024 UTC