Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:23845 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 23721 invoked by uid 1010); 1 Jun 2006 08:15:39 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 23706 invoked from network); 1 Jun 2006 08:15:39 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 1 Jun 2006 08:15:39 -0000 X-PHP-List-Original-Sender: andi@zend.com X-Host-Fingerprint: 80.74.107.235 mail.zend.com Linux 2.5 (sometimes 2.4) (4) Received: from ([80.74.107.235:61809] helo=mail.zend.com) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id 00/50-07504-A22AE744 for ; Thu, 01 Jun 2006 04:15:39 -0400 Received: (qmail 11432 invoked from network); 1 Jun 2006 06:28:32 -0000 Received: from localhost (HELO ANDI-NOTEBOOK.zend.com) (127.0.0.1) by localhost with SMTP; 1 Jun 2006 06:28:32 -0000 Message-ID: <7.0.1.0.2.20060531232613.03cd05c8@zend.com> X-Mailer: QUALCOMM Windows Eudora Version 7.0.1.0 Date: Wed, 31 May 2006 23:28:49 -0700 To: "Steph Fox" ,"Frank M. Kromann" Cc: "'internals'" , "'Antony Dovgal'" ,"Dmitry Stogov" , "'Xuefer'" In-Reply-To: <09f801c68536$f18f0cd0$6602a8c0@foxbox> References: <11490874854760000@9866357972520000.9866341568840000> <091901c684c6$390ef370$6602a8c0@foxbox> <7.0.1.0.2.20060531212500.03758ec8@zend.com> <09f801c68536$f18f0cd0$6602a8c0@foxbox> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: Re: [PHP-DEV] tsrm_shutdown() and the CLI SAPI From: andi@zend.com (Andi Gutmans) As we are not planning to release a new version within the next couple of weeks, I suggest before jumping to conclusions we take a look at it. If you really need to comment out that line in the meanwhile that's OK with me. Andi At 09:50 PM 5/31/2006, Steph Fox wrote: >>>Yes, it would, given the root cause - but would you really want to >>>break the whole of PHP for an academic exercise? >> >>It's not really an academic exercise. If we know there's a bug >>someplace we should at least look into it and try and understand it. > >Frank's referring to Zeev's three-years-ago decision to simply opt >out of tsrm_shutdown() here... he's suggesting we revert it. > >>Then if we decide to remove the trsm_shutdown call for a good >>reason (circular dependency, blah blah blah) then we can do that >>and put a nice fat comment on why it's the right thing to do. But I >>do think it's benefical to try and understand what's happening. > >Fine, but breaking working code while you're trying to understand >what's happening is far from beneficial to our users. Can't we at least #0 it? > >> >>Andi