Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:48827
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain pooteeweet.org from 188.40.37.16 cause and error)
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=us-ascii
In-Reply-To: <16FA8F9A-E36B-4057-BBCC-D6CC9C8D6D8B@php.net>
Date: Fri, 18 Jun 2010 16:28:31 +0200
Cc: Stas Malyshev <smalyshev@sugarcrm.com>,
 Christian Kaps <christian.kaps@mohiva.com>,
 "internals@lists.php.net" <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <3C5F598B-3E72-4959-B774-2FD62C1BC99F@pooteeweet.org>
References: <4C1A6B47.4060702@mohiva.com> <4C1A7400.6010800@sugarcrm.com> <16FA8F9A-E36B-4057-BBCC-D6CC9C8D6D8B@php.net>
To: Melanie Rhianna Lewis <cyberspice@php.net>
Subject: Re: [PHP-DEV] Type hinting
From: mls@pooteeweet.org (Lukas Kahwe Smith)


On 18.06.2010, at 16:13, Melanie Rhianna Lewis wrote:

>=20
>=20
> On 17 Jun 2010, at 20:14, Stas Malyshev wrote:
>=20
>> 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.
>=20
> 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.


isnt this what interfaces are for?

regards,
Lukas Kahwe Smith
mls@pooteeweet.org