Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:55385
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain nebm.ist.utl.pt from 193.136.128.22 cause and error)
Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes
To: internals@lists.php.net
References: <4E6D0B5C.8030907@php.net>
 <op.v1n0lttyidpuyk@cataphract.cata.lo.geleia.net> <4E6DF2A9.2040608@php.net>
Date: Mon, 12 Sep 2011 14:43:33 +0100
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Organization: =?utf-8?Q?N=C3=BAcleo_de_Eng=2E_Biom=C3=A9di?=
 =?utf-8?Q?ca_do_I=2ES=2ET=2E?=
Message-ID: <op.v1o62vdcidpuyk@clk-0081.mshome.net>
In-Reply-To: <4E6DF2A9.2040608@php.net>
User-Agent: Opera Mail/11.51 (Win32)
Subject: Re: [PHP-DEV] [RFC] Factory for Stream Wrappers
From: glopes@nebm.ist.utl.pt ("Gustavo Lopes")

Em Mon, 12 Sep 2011 12:53:13 +0100, Sebastian Bergmann <sebastian@php.net>  
escreveu:

>  Regarding state it is important to notice that PHP does *not* execute
>  the constructor on all low level calls when instantiating the wrapper
>  class - for whatever reason that is the case. Changing that behaviour
>  would cause quite some side effects, with possible quite some BC breaks.

This is a bit off-topic, but could you elaborate on this (possibly  
submitting a bug report)? I see user_wrapper_opener trying to call the  
constructor:

http://lxr.php.net/opengrok/xref/PHP_5_3/main/streams/userspace.c#298

So any failure to do this would be a bug.

BTW, another advantage of the proposed change is that you can have stream  
wrappers with constructors that take arguments. For the record, I'm in  
favor of this, even though I don't buy the testability claim. My point  
yesterday was mainly the RFC did not explain the advantages very clearly.

-- 
Gustavo Lopes