Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:46087
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.210.192 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type;
        b=SP0NR6W/F5xUibckaiuGz5J9+cBKPG3UxxYh0WM7lHHnQCDmyksRj6WSAyqABmWGOy
         CZA5sDTYcWYfLcRVFcKu+WO87TIViB89iy5O1tFiTjy2qMgewrX4FcVFJVAp6ug97QxL
         Q1z+VTgILmyjnT3590EqU8Ffpb+oHXjoWPQb8=
MIME-Version: 1.0
In-Reply-To: <4B042CBB.9070701@easyflirt.com>
References: <E0EDC434-695E-43BF-BFBC-B4E60F98D84B@typo3.org>
	 <4B0426A9.4000806@easyflirt.com>
	 <e666c3890911180900q3408f3f4t3fc140e8dfc0c242@mail.gmail.com>
	 <4B042CBB.9070701@easyflirt.com>
Date: Wed, 18 Nov 2009 18:41:28 +0100
Message-ID: <b1d36f000911180941w1b9f22b0i1cb59c9620416e94@mail.gmail.com>
To: Mathieu Suen <mathieu.suen@easyflirt.com>
Cc: internals@lists.php.net
Content-Type: multipart/alternative; boundary=001485f89e529adce20478a8c056
Subject: Re: [PHP-DEV] RFC: Custom Factories (SPL)
From: eloybote@gmail.com (Eloy Bote Falcon)

--001485f89e529adce20478a8c056
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

2009/11/18 Mathieu Suen <mathieu.suen@easyflirt.com>

> Etienne Kneuss a =E9crit :
>
> Hello,
>>
>> On Wed, Nov 18, 2009 at 5:54 PM, Mathieu Suen <mathieu.suen@easyflirt.co=
m
>> >wrote:
>>
>> Robert Lemke a =E9crit :
>>>
>>>  Hi folks,
>>>
>>>> after discussing the idea with various PHP developers I now felt safe
>>>> enough that it's not a completely stupid idea to post an RFC for it. T=
he
>>>> idea is to add support the registration of custom factories which are
>>>> responsible for instantiating certain classes.
>>>>
>>>> Here is the first draft of my RFC:
>>>> http://wiki.php.net/rfc/customfactories
>>>>
>>>> I suggest that we first discuss the implications and usefulness of thi=
s
>>>> feature. In a second step I'd need to find some skilled internals wiza=
rd
>>>> who
>>>> can implement it, because not being a C developer myself, all I can
>>>> offer is
>>>> making suggestions and fine coffee.
>>>>
>>>> Looking forward to hearing your comments!
>>>> Robert
>>>>
>>>>
>>>> An other way maybe to allow this:
>>>
>>> $email =3D new $emailClassName();
>>>
>>>
>>>
>>> This is already allowed.
>>
>> Best,
>>
>>
>
> Right!!
> I get confused with:
> $classNamme::getInstance();
>
> So you can easily inject dependency:
>
> class Foo {
>
>        protected $emailer;
>
>        public function __construct($emailClass) {
>                $this->emailer=3D $emailClass;
>        }
>
>        public function bar() {
>                // $email =3D new $this->emailer(); Of course not allowed
>                $emailer =3D $this->emailer;
>                $email =3D $emailer();
>                // ...
>
>        }
> }
>
> -- Mathieu Suen
>

Well, $email =3D new $this->emailer(); it's allowed too, and behaves as
expected since FOO::emailer it's a string.


Reagards,

Eloy Bote.

--001485f89e529adce20478a8c056--