Hi! On 9/19/11 3:20 AM, Pierre Joye wrote:
If we talk about implementing the abstract concept and we use the interface model to do it, then we do it wrong. I'm out of other arguments, or maybe one new one, if we implement abstract like interface, then let kill abstract support, we don't need that.
Interface defines protocol without any implementation. Abstract class defines both class template and protocol with partial implementation. These are different things, and regardless of signature discussion - which really has nothing to do with the difference between abstracts and interfaces - one of them does not replace the other in any way. You could simulate abstracts with interfaces, but that would be abuse of the interface idea.
-- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227 -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
