Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:17593
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <20050808141732.lienuuns5ds4w0ks@hristov.com>
Date: Mon, 08 Aug 2005 14:17:32 +0200
To: Derick Rethans <derick@php.net>
Cc: PHP Developers Mailing List <internals@lists.php.net>
References: <Pine.LNX.4.62.0508081150140.2940@localhost>
In-Reply-To: <Pine.LNX.4.62.0508081150140.2940@localhost>
MIME-Version: 1.0
Content-Type: text/plain;
	charset=windows-1251;
	format="flowed"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
User-Agent: Internet Messaging Program (IMP) H3 (4.0)
Sender: <cpanel@iko.gotobg.net>
Subject: Re: [PHP-DEV] type hinting throwing a fatal error
From: php@hristov.com (Andrey Hristov)

  Hmm,
I was complaining about inusaability ot type hinting because of this fatal
errors but nobody seems heard me :(. One better do a check in the code than
risking a fatal error which is unstoppable...
I call this showstopper if we say that we are proud with the type-hinting.

Andrey


Quoting Derick Rethans <derick@php.net>:

> 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
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>