expected result:

string(1) "1"
string(1) "2"
string(1) "3"
string(1) "4"
string(1) "5"
string(1) "6"
string(1) "7"
string(1) "8"
Array
(
    [0] => stdClass Object
        ( 
            [1] => 0
            [2] => 0
            [3] => 0
            [4] => 0
            [5] => 0
            [6] => 0
            [7] => 0
            [8] => 0
        )

    [1] => stdClass Object
        (
            [1] => 0
            [2] => 0
            [3] => 0
            [4] => 0
            [5] => 0
            [6] => 0
            [7] => 0
            [8] => 0
        )

)

I don't understand this bug report.  I see this in $_GET:

Array
(
    [ang] => Array
        (
            [1] => 79
            [2] => 786
            [3] => 
            [4] => 
            [5] => 89
            [6] => 
            [7] => 
            [8] => 
        )

    [ver] => Array
        (
            [1] => 
            [2] => 
            [3] => 78786
            [4] => 8
            [5] => 8
            [6] => 445
            [7] => 3
            [8] => 
        )

)

That looks correct to me.

Yes, but this:

        for ($i=1;8 >= $i;$i++) 
        { 
            $ang->$i *= $ang_fak; 
            $ver->$i *= $ver_fak; 
        } 

creates a new index (string), and don't overwrite the old index (int), and also there are two indexes of the same value (but two different types int and string)

Right, so your bug report is just a really obfuscated way of reporting this:


$a = array(1=>'abc');
$b = (object)$a;
$i=1;
$b->$i = 'def';
var_dump($b);


which shows the inherent side-effects of casting an array to an object 
indiscriminately.  This is just how it works.  You can kinda-sorta fake numeric 
properties if you try hard, but it is a bad idea.  Fix your code to do:

$a = array('1'=>'abc');
$b = new stdclass;
foreach($a as $k=>$v) $b->$k = $v;
$i=1;
$b->$i = 'def';
var_dump($b);

instead of expecting casting to do the right thing.  Or if you know you are 
going to be using the array as an object, use string indices.  Like a1, a2, a3..

But this is very slow. Why don't you can fix type casting from array to object? When int-indexes are always converted to string-indexes this problem will disappear?

Or why are numeric indexes allowed in classes? When numeric index are disabled in classes indexes are always (?) strings?

The fix for this bug has been committed.

Snapshots of the sources are packaged every three hours; this change
will be in the next snapshot. You can grab the snapshot at
http://snaps.php.net/.

 For Windows:

http://windows.php.net/snapshots/
 
Thank you for the report, and for helping us make PHP better.

Fixed by: https://wiki.php.net/rfc/convert_numeric_keys_in_object_array_casts