Interesting.. in reality it IMHO should abort with a fatal error when classes are named __construct, __destruct, __call, __callStatic, __get, __set, __isset, __unset, __sleep, __wakeup, __toString, __set_state and __clone.

Personally, i dont see why you would raise a fatal error when using magic methods for class names, you're not conflicting with anything, it should allow you to use it as normal.

Think about it for a minute. If you class is called '__call' and you declare a function '__call', that one would be the constructor right? The error you experience is that you are calling the constructor without the parameters it expects.
Check this code:

<?php

class __call {

	public function __call($method, $args){
		echo $method."\n";
	}

    public function test() {
        echo "i am test\n";
    }

}

$obj = new __call('my method','arguments');
$obj->test();

?>

So, either PHP should not allow a class to have the same name as magic methods, or you need to play with the idea that the constructor comes first.
Other 'workaround' for this would be:

<?php

class __call {

    public function __construct(){}

	public function __call($method, $args){
		echo $method."\n";
	}

    public function test() {
        echo "i am test\n";
    }

}

$obj = new __call('my method','arguments');
$obj->test();

$obj2 = new __call;

?>

Now you have a __construct() function, so __call can be used normally.

Regards,

Henrique

Henrique,

Thanks for that, i completely forgot about the php4 backwards compatibility. I havent used php4 in so long that it totally slipped my mind.

Bug set as bogus.