Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:55547
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.45 as permitted sender)
MIME-Version: 1.0
Sender: ekneuss@gmail.com
In-Reply-To: <op.v11v9azwidpuyk@clk-0081.mshome.net>
References: <CAKUjMCXiYc63NKsUuYWXT-A-aPabdPV6142LP9h4-c=2aUxW=w@mail.gmail.com>
	<4E74E5A0.2030006@sugarcrm.com>
	<alpine.DEB.2.02.1109181708480.3630@whisky>
	<4E76320F.6010904@sugarcrm.com>
	<CAF+90c8oZ4ghsFBa7jHtp_AKqD0N0cDhMycpjFTpCkLV9qRsqQ@mail.gmail.com>
	<4E764137.9080507@sugarcrm.com>
	<CAEZPtU6yBMP3X8_EpUXauDifAWEJwXS4fki5HtYNybWoCQ0kFw@mail.gmail.com>
	<4E7685DE.6010805@sugarcrm.com>
	<CAEZPtU6LvwM+qDCKQr+XOUu8Ab+QK2=hbkykD_d=jWiAwB8ozA@mail.gmail.com>
	<4E768C86.3030307@sugarcrm.com>
	<CAEZPtU4SONqYvAnj739-NdDYC=9DGkLrC=_cB-Ay6KJEbTpJZg@mail.gmail.com>
	<4E769418.6040200@sugarcrm.com>
	<CAEZPtU54b=aymn26V-xxHEm1Xb6MiSgvPC8By2+++MZyyDvJ7A@mail.gmail.com>
	<4E770163.2090001@sugarcrm.com>
	<CAEZPtU6_fg76YSPQ+j42KnC1LQGrKoz81r5pb2_4h7Zn6Q2g9Q@mail.gmail.com>
	<4E770770.60809@sugarcrm.com>
	<CAEZPtU6aExvyyurnwA69=KWGR3Qs+gMxs9_LYO0ws8cm67j-ag@mail.gmail.com>
	<CACQesk7XGWvPgH-8+X0berWh8_ZADT_bc8eoeN+8Y0+Sm0RZOg@mail.gmail.com>
	<CACQesk4kxo1PSaY=6v0q3CSXcDSfk9oT5zRezXF3yFfuzyCN_g@mail.gmail.com>
	<op.v11v9azwidpuyk@clk-0081.mshome.net>
Date: Mon, 19 Sep 2011 12:40:16 +0200
Message-ID: <CACQesk71yLDm70uLcKry6_08h8-OJSiber13nh6Xnzyfj=tY=Q@mail.gmail.com>
To: Gustavo Lopes <glopes@nebm.ist.utl.pt>
Cc: internals@lists.php.net
Content-Type: multipart/alternative; boundary=0015174c113cffa70604ad48f76e
Subject: Re: [PHP-DEV] __constructor parameter limitations.
From: colder@php.net (Etienne Kneuss)

--0015174c113cffa70604ad48f76e
Content-Type: text/plain; charset=UTF-8

Hi,

On Mon, Sep 19, 2011 at 12:18, Gustavo Lopes <glopes@nebm.ist.utl.pt> wrote:

> Em Mon, 19 Sep 2011 10:56:03 +0100, Etienne Kneuss <colder@php.net>
> escreveu:
>
>
>
>> Apparently you guys are speaking about the initial implementation of an
>> abstract method, while I was talking about overriding a method, which is
>> not the relly same. So the above doesn't really apply.
>>
>> The initial implementation of an abstract method should match the
>> signature,
>> while overriding a method should be able to loosen the precondition in
>> many ways (type hints change, less arguments, etc..), IMO.
>>
>>
> I should like to hear why. As far as I can see, there's absolutely no
> difference. All I've seen in this thread to this respect are semantic
> pseudo-arguments.
>

Well it is about semantics, and IMO defining a method as abstract is some
sort of declaration, and this declaration should be respected when the
method is actually implemented.

On the other hand, interfaces define usage capabilities, and those usages
should work.

There might be close to no difference in the way the are internall handled
currently, but IMO there is a semantic difference between the two.


> I'd say interfaces are much more likely to include more useless parameters
> than a concrete method definition, which most likely will only include the
> arguments it actually needs.
>
> An example:
>
> http://www.google.com/**codesearch#HmA4mAI_aLc/src/**
> main/java/terrastore/server/**impl/support/**JsonBucketsProvider.java&q=**
> implements%5C%**20MessageBodyWriter&type=cs&l=**36<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).
>
> --
> Gustavo Lopes
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>


-- 
Etienne Kneuss
http://www.colder.ch

--0015174c113cffa70604ad48f76e--