Description:
------------
---
First at manual page: http://se1.php.net/manual/en/control-structures.foreach.php
Then to: http://stackoverflow.com/questions/4100488/a-numeric-string-as-array-key-in-php
Finally from manual page: http://www.php.net/language.types.array
---

The key can either be an integer or a string. (<- period)

Remove key casts on arrays so that floats, booleans and null also result in a warning (Illegal offset type), but mainly so that "1" remains a string.

When defining an array, like with a variable, it should be created just the way the programmer types it. Why is there an identical operator if it can't be used in this case? I know this "behaviour" is mentioned in the manual, but as I've been using many other languages over the years, it seems utterly meaningless to be forced to read the entire manual and note every detail to learn that this kind of irregularity exists. Automatic type casting is acceptable when performing an evaluation with ==, but at definition.. that's just sad.


Test script:
---------------
$foo = array("123" => 1);
var_dump($foo);

/*
Therefore, this fails:
foreach ($foo as $key => $value) {
  echo ($key === "123" ? "success" : "fail");
}
*/


Expected result:
----------------
array(1) {
  ["123"]=>
  int(1)
}


Actual result:
--------------
array(1) {
  [123]=>
  int(1)
}