Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:10838 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 19392 invoked by uid 1010); 29 Jun 2004 20:32:00 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 19288 invoked from network); 29 Jun 2004 20:32:00 -0000 Received: from unknown (HELO distance.intux.org) (213.239.198.8) by pb1.pair.com with SMTP; 29 Jun 2004 20:32:00 -0000 Received: (qmail 11395 invoked from network); 29 Jun 2004 20:26:58 -0000 Received: from unknown (HELO silverbox) (intux?org?fschaper@82.82.158.45) by distance.intux.org with SMTP; 29 Jun 2004 20:26:58 -0000 Message-ID: <004901c45e18$0cc8f8a0$c501a8c0@silverbox> To: "Marcus Boerger" , References: <000b01c45d02$95eab040$9f00a8c0@silverbox> <1357343140.20040629195517@marcus-boerger.de> Date: Tue, 29 Jun 2004 22:31:25 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1409 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 Subject: Re: [PHP-DEV] __Destruct() functionality From: fschaper@intux.org ("Florian Schaper") Marcus Boerger wrote: > Hello Florian, > > there is no problem in calling resource destructors/terminators in > your destructors. You simply cannot output text to your pages from > them. If this is not true then we need to fix it. For example if an > object of yours holds a database connection and your destructor > executes some SQL code this must work. Open a bug report if necessary. > Well you can output text in destructors. All other functions are also available but _might_ not behave the way we would expect them to. I was wrong regarding the mysql extension - (really bad guesswork on my part). However if I'm not wrong this time (again I might, since I have no dev. environment with me right now to check back with the sources) the extensions PHP_RSHUTDOWN_FUNCTION is called _before_ object destructors are called. That seems now to be the problem already stated in "documentation" bug ( #27555 ). Developers might well clean up their stuff at that point in the extension (like write the session to disk in the session ext.) expecting the session to be "over" what leads to confusing results for people (extension and php developers alike) when it actually isn't. ./regards Florian