Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:55482
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.177 as permitted sender)
MIME-Version: 1.0
Sender: laruence@gmail.com
In-Reply-To: <CACQesk71k5ff0a8D8K2T5d7UB3HFjK+0Ggoa+E+_dwRQ8k65Aw@mail.gmail.com>
References: <CAKUjMCXiYc63NKsUuYWXT-A-aPabdPV6142LP9h4-c=2aUxW=w@mail.gmail.com>
 <CAF+90c-YsWFtZVPajiUL6SKvde=EyVsSGAgWZrCCvT3Y9Q9YCw@mail.gmail.com>
 <CAET_qdOGZ1YUtE_X4gMDnPOTtw15h_fcMsQKY5jpZrDkvoscvg@mail.gmail.com>
 <CABBJUpfHKHsP-btD33wR2+b=WZMJ1iMzULYuKjkQLTALU6HSog@mail.gmail.com> <CACQesk71k5ff0a8D8K2T5d7UB3HFjK+0Ggoa+E+_dwRQ8k65Aw@mail.gmail.com>
Date: Sat, 17 Sep 2011 23:20:17 +0800
Message-ID: <CABBJUpfonuV7=Fsv3j-T3uws2tM0FHQbWUG9ntr2BrpiCfDBUg@mail.gmail.com>
To: Etienne Kneuss <colder@php.net>
Cc: devis@lucato.it, internals@lists.php.net, RQuadling@gmail.com, 
	Nikita Popov <nikita.ppv@googlemail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] __constructor parameter limitations.
From: laruence@php.net (Laruence)

2011/9/17 Etienne Kneuss <colder@php.net>:
>
>
> On Sat, Sep 17, 2011 at 17:08, Laruence <laruence@php.net> wrote:
>>
>> 2011/9/17 =C2=A0<devis@lucato.it>:
>> > Hi,
>> >
>> > I think Richards intended other methods often used in combination with
>> > __construct:
>> >
>> > class A =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 { public function init($a, =
$b) { } }
>> > class B extends A { public function init($a) { } }
>> >
>> > =3D> PHP Strict Standards: =C2=A0Declaration of B::init() should be co=
mpatible
>> > with
>> > that of A::init()
>> =C2=A0do you know any reason for this?
>
> The reason for this is simply that B must act like A since every B object=
 is
> also an object of A.
sure, but why we need interface?   in addition,  I don't think this
can be done by  restricting  the argument

thanks
>
>>
>> >
>> > The example with __construct() is valid (at least in 5.3).
>> >
>> >
>> > Devis
>> >
>> >
>> > On 17 September 2011 14:43, Nikita Popov <nikita.ppv@googlemail.com>
>> > wrote:
>> >
>> >> Hi Richard!
>> >>
>> >> Which change are you talking about? I just tried doing:
>> >> =C2=A0 =C2=A0<?php
>> >> =C2=A0 =C2=A0class A =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 { public func=
tion __construct($a) =C2=A0 =C2=A0 { } }
>> >> =C2=A0 =C2=A0class B extends A { public function __construct($a, $b) =
{ } }
>> >> And it worked on 5.4 Beta 1 without errors.
>> >>
>> >> Nikita
>> >>
>> >> On Sat, Sep 17, 2011 at 3:27 PM, Richard Quadling <rquadling@gmail.co=
m>
>> >> wrote:
>> >> > Hi.
>> >> >
>> >> > With the recent BC with regard the locking of the constructor's
>> >> > signature for subclasses, what is the expected mechanism for allowi=
ng
>> >> > a subclass to have additional parameters?
>> >> >
>> >> > You can always supply them and use func_get_args() / func_num_args(=
)
>> >> > /
>> >> > etc. to read them.
>> >> >
>> >> > It would seem that the limitation restricts the capabilities. I'm n=
ot
>> >> > a purist. Software development is a compromise between purity and
>> >> > getting the job done in an efficient and understandable manner.
>> >> >
>> >> > By allowing undocumented parameters to the constructor (due to the
>> >> > enforced signature), this would seem to break things on a different
>> >> > front (I can't docblock non defined parameters for examples).
>> >>
>> >> --
>> >> PHP Internals - PHP Runtime Development Mailing List
>> >> To unsubscribe, visit: http://www.php.net/unsub.php
>> >>
>> >>
>> >
>>
>>
>>
>> --
>> Laruence =C2=A0Xinchen Hui
>> http://www.laruence.com/
>>
>> --
>> PHP Internals - PHP Runtime Development Mailing List
>> To unsubscribe, visit: http://www.php.net/unsub.php
>>
>
>
>
> --
> Etienne Kneuss
> http://www.colder.ch
>



--=20
Laruence =C2=A0Xinchen Hui
http://www.laruence.com/