Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:17581
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Date: Mon, 8 Aug 2005 11:50:20 +0200 (CEST)
To: PHP Developers Mailing List <internals@lists.php.net>
Message-ID: <Pine.LNX.4.62.0508081150140.2940@localhost>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: type hinting throwing a fatal error
From: derick@php.net (Derick Rethans)

Hei,

currently if you pass a wrong object's type to a typehinted parameter:

	derick@kossu:~$ cat /tmp/foo.php
	<?php
	class foo {
	        function bar(foo $a)
	        {
	        }
	}

	$a = new foo;
	$a->bar(new stdClass);
	?>
	derick@kossu:~$ php /tmp/foo.php

	Fatal error: Argument 1 must be an instance of foo in /tmp/foo.php on 
	line 3

As type hinting is a new OO thing, it might perhaps make some sense to 
make this an exception instead - as this error might also happen for 
dynamic things by people who use the classes you designed. In that case 
having this fatal error to stop the whole application can be annoying. 
Opinions?

Derick