Em Mon, 19 Sep 2011 11:20:56 +0100, Pierre Joye <pierre....@gmail.com>
escreveu:
On Mon, Sep 19, 2011 at 12:18 PM, Gustavo Lopes <glo...@nebm.ist.utl.pt>
wrote:
http://www.google.com/codesearch#HmA4mAI_aLc/src/main/java/terrastore/server/impl/support/JsonBucketsProvider.java&q=implements%5C%20MessageBodyWriter&type=cs&l=36
This is the most common scenario for implementations of this interface
(see the other search results).
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.
There's no significant difference between interfaces and abstract classes
here. Abstract classes frequently have protected hook methods you can
override/implement take more arguments that you need. For instance, you
could have:
class Form {
...
abstract protected function buildHTML($page, $errors, $params, $command);
...
}
and reasonably not need all the arguments.
--
Gustavo Lopes
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
