Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:55530
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.213.42 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <op.v11s7igeidpuyk@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>
	<op.v11rqdgiidpuyk@clk-0081.mshome.net>
	<CACQesk5iSTqw4r4OVyCG5WYyYz3xie4ionhRBVj2-r_iDgznQg@mail.gmail.com>
	<op.v11s7igeidpuyk@clk-0081.mshome.net>
Date: Mon, 19 Sep 2011 11:30:48 +0200
Message-ID: <CAH-PCH4-JBSnLoBW9hpk1jHmk46oXXgc+D=bkFoHiLLDXm8kbQ@mail.gmail.com>
To: Gustavo Lopes <glopes@nebm.ist.utl.pt>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] __constructor parameter limitations.
From: tyra3l@gmail.com (Ferenc Kovacs)

On Mon, Sep 19, 2011 at 11:12 AM, Gustavo Lopes <glopes@nebm.ist.utl.pt> wr=
ote:
> Em Mon, 19 Sep 2011 10:01:32 +0100, Etienne Kneuss <colder@php.net>
> escreveu:
>
>> Sure, but you mix two things here, references would have to be handled
>> specifically, and we would not allow to specify less args by ref.
>>
>> There is simply no reason for disallowing this with nornal args though.
>> Imagine the following code:
>>
>> interface Foo { public function plop ($a,$b,$c,$d) }
>>
>> class A implements Foo {
>> =C2=A0 public function plop() {
>> =C2=A0 =C2=A0 =C2=A0$args =3D func_get_args();
>> =C2=A0 =C2=A0 =C2=A0// ...
>> =C2=A0 }
>> }
>>
>> This is perfectly valid PHP code, there is no valid usage of Foo that wi=
ll
>> not work with A... So to me this restriction seems really arbitrary.
>> And I don;t believe missing an argument in the declaration of a method,
>> using it in the body of the method and not realising it is so much of a
>> common error that it would warrant this.
>>
>
> Arbitrary as it may be, it's nevertheless reasonably arbitrated given how
> little useful it is to just ignore arguments and how likely it is to a
> mistake.
>
> And I don't buy the func_get_args() argument. Why would anyone use
> func_get_args for anything other than variadic functions?... I certainly
> don't.
>

Lester mentioned another use-case, when the Subclass will call the
parent method with constant values as arguments.
For example I have Quadrilateral Superclass with the public function
__construct($width, $height){}
If I create a more special Subclass: Square, I can omit the second
parameter, as I know that for Square, the $width and $height is equal.

--=20
Ferenc Kov=C3=A1cs
@Tyr43l - http://tyrael.hu