Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:42914
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: softfail (pb1.pair.com: domain ctindustries.net does not designate 207.58.142.213 as permitted sender)
Message-ID: <4989A5D6.5010201@ctindustries.net>
Date: Wed, 04 Feb 2009 09:27:34 -0500
User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209)
MIME-Version: 1.0
To: Sebastian Bergmann <sb@sebastian-bergmann.de>
CC: internals@lists.php.net
References: <5EC76153-898F-49C2-BDF1-C227578DB874@pooteeweet.org> <298CA3D0-60B7-4CFD-A2D3-E39D52ECDD46@bitextender.com> <49898DBE.7050200@php.net> <gmc80q$h86$1@ger.gmane.org>
In-Reply-To: <gmc80q$h86$1@ger.gmane.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] towards the next 5.3 release
From: rrichards@ctindustries.net (Rob Richards)

Sebastian Bergmann wrote:
> Rob Richards wrote:
>   
>> The addition in 5.2.6 was a BC break and is fixed in 5.2.9
>>     
>
>  Removing the type-hint is only a short-term fix, IMHO. A better solution
>  would be to introduce a marker interface that is implemented by the
>  respective classes of the XML extensions involved and use said
>  interface in the type hint.
>
>   
If that's the route this is going to go, I'd rather be able to set an 
anytype hint where the developer could possibly restrict this further 
with a more specific type if they extend the class.

Rob