Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:60611 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 86959 invoked from network); 18 May 2012 15:54:30 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 18 May 2012 15:54:30 -0000 Authentication-Results: pb1.pair.com smtp.mail=johannes@schlueters.de; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=johannes@schlueters.de; sender-id=unknown Received-SPF: error (pb1.pair.com: domain schlueters.de from 217.114.211.66 cause and error) X-PHP-List-Original-Sender: johannes@schlueters.de X-Host-Fingerprint: 217.114.211.66 config.schlueters.de Received: from [217.114.211.66] ([217.114.211.66:33839] helo=config.schlueters.de) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 4C/66-54140-4B076BF4 for ; Fri, 18 May 2012 11:54:29 -0400 Received: from [192.168.2.230] (host-188-174-212-19.customer.m-online.net [188.174.212.19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by config.schlueters.de (Postfix) with ESMTPSA id C5CB161E0D; Fri, 18 May 2012 17:54:25 +0200 (CEST) To: Jorrit Schippers - nCode Cc: internals@lists.php.net In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Date: Fri, 18 May 2012 17:54:21 +0200 Message-ID: <1337356461.1699.24.camel@guybrush> Mime-Version: 1.0 X-Mailer: Evolution 2.30.3 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Old bug 40459: Stat and Dir stream wrapper methods do not call constructor From: johannes@schlueters.de (Johannes =?ISO-8859-1?Q?Schl=FCter?=) Hi, On Fri, 2012-05-18 at 12:42 +0200, Jorrit Schippers - nCode wrote: > So my question is: can anyone familiar with the Stream Wrapper code take > a look at this issue? My C is not of sufficient level to fix this > myself. My idea would be to abstract creating a stream wrapper instance > and invoking the constructor to a separate function and calling that > function from the various functions that use stream wrappers, as the > amount of code needed to construct an instance and call the constructor > seems quite high to copy everywhere. "Fixing" this is quite trivial.. except that it breaks any code depending on the current behavior where people are using the constructor in a way which might have an bad impact. This could only be done in master. Sometime ago I stumbled over that behavior it and had an additional issue preventing me from fixing it, which I don't remember right now ... johannes