reproduced with PHP 4.0.6RC1.

The result of implode() is in a wrong order, if a "named index" is used.
Example exploding and imploding a string (seperated by "+"):

$a = "11+12+13+14";
	
  echo ("a befor execution: ".$a."<BR>");
  echo ("this works: ".implode("+", explode("+", $a))."<BR>");

  list(
    $r["A"],
    $r["B"],
    $r["C"],
    $r["D"]) = explode("+", $a);

  echo ("r between execution: ".$r["A"].$r["B"].$r["C"].$r["D"]."<BR>");

  $a = implode("+", $r);
  echo ("a after execution: ".$a."<BR>");

Output:
a befor execution: 11+12+13+14
this works: 11+12+13+14
r between execution: 11121314
a after execution: 14+13+12+11

The values in the last row have the wrong order.

The problem: list(<a>,<b>) will assign to <b> first, and only then to <a>.

This is the case in all versions of PHP 4 (don't know for PHP 3). Usually this assignment order doesn't matter, but in this case it does.

(reclassified, analyzed now (was already marked analyzed?))

<?php
list($ar['a'],$ar['b']) = array(1,2);

var_dump($ar);
?>
array(2) {
  ["b"]=>
  int(2)
  ["a"]=>
  int(1)
}

Honestly, I think changing this now in PHP4 is bad. It behaved that way since 4.0, so changing it with 4.3 is just silly. This asks for more trouble that we would gain.

Moving over to documentation problem.

This bug has been fixed in CVS. You can grab a snapshot of the
CVS version at http://snaps.php.net/. In case this was a documentation 
problem, the fix will show up soon at http://www.php.net/manual/.
In case this was a PHP.net website problem, the change will show
up on the PHP.net site and on the mirror sites.
Thank you for the report, and for helping us make PHP better.