Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:9370
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <4083A9E3.4070504@cschneid.com>
Date: Mon, 19 Apr 2004 12:28:51 +0200
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040114
MIME-Version: 1.0
To: zeev@zend.com
Cc: Andi Gutmans <andi@zend.com>, internals@lists.php.net
References: <5.1.0.14.2.20040419112627.03efaa00@localhost> <5.1.0.14.2.20040419130523.04e3fe60@localhost>
In-Reply-To: <5.1.0.14.2.20040419130523.04e3fe60@localhost>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Interface inheritance
From: cschneid@cschneid.com (Christian Schneider)

Zeev Suraski wrote:
> 1.  First of all, I agree that in a perfect world we should go with 
> E_COMPILE_ERROR for everything.  Maybe now that's constructors are out 

I'm not sure I understand what you mean by everything.

> whole interface/abstract/class type hints mechanism was added for the 
> sole reason of enforcing prototypes, and effectively, it is pretty much 

Concerning interface/abstract classes I can see you reasoning for 
enforcing the prototype. Personally I don't feel like using interfaces 
and abstract classes but as it is implemented in PHP5 it should be done 
right. Make whips and chains people suffer fully from their bondage 
addiction :-)

For class type hints (this is specifying the parameter type in your 
function definition, right?) I think it should be enforced for *calling* 
but not for extending. A specialized class often leaves out parameters 
of the generic base class. E.g. db_record_foo may extend db_record which 
takes the table as an argument which will always be foo for the 
specialized class and hence left out there.

Does that make sense?

- Chris