Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:48826
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 85.158.45.55 as permitted sender)
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=us-ascii
In-Reply-To: <4C1A7400.6010800@sugarcrm.com>
Date: Fri, 18 Jun 2010 15:13:21 +0100
Cc: Christian Kaps <christian.kaps@mohiva.com>,
 "internals@lists.php.net" <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <16FA8F9A-E36B-4057-BBCC-D6CC9C8D6D8B@php.net>
References: <4C1A6B47.4060702@mohiva.com> <4C1A7400.6010800@sugarcrm.com>
To: Stas Malyshev <smalyshev@sugarcrm.com>
Subject: Re: [PHP-DEV] Type hinting
From: cyberspice@php.net (Melanie Rhianna Lewis)



On 17 Jun 2010, at 20:14, Stas Malyshev wrote:

> Hi!
>=20
>> I know the discussion is about scalar type hints. But what is with a
>> object type hint as base for all objects?
>=20
> When it makes sense to accept any object, regardless of the class, but =
not other types? I wonder if it's really a common use-case.

Its useful in some patterns.  For example suppose you have a pattern =
where a class wraps another class.  The wrapped class could be *any* =
class if you're modify the behaviour of some default methods (say doing =
something like a decorator pattern).  Having a type hint that recognises =
object vs non objects is useful.

Melanie