Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:10839
Return-Path: <gareth@fission.org.uk>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 21313 invoked by uid 1010); 29 Jun 2004 23:50:58 -0000
Delivered-To: ezmlm-scan-internals@lists.php.net
Delivered-To: ezmlm-internals@lists.php.net
Received: (qmail 21259 invoked from network); 29 Jun 2004 23:50:58 -0000
Received: from unknown (HELO stack.fission.org.uk) (195.82.120.217)
  by pb1.pair.com with SMTP; 29 Jun 2004 23:50:58 -0000
Received: from cpc4-oxfd3-3-0-cust191.oxfd.cable.ntl.com ([213.107.70.191] helo=[192.168.10.254])
	by stack.fission.org.uk with esmtp (Exim 3.36 #1 (Debian))
	id 1BfSL7-0008GB-00; Wed, 30 Jun 2004 00:48:37 +0100
To: Marcus Boerger <helly@php.net>
Cc: Florian Schaper <fschaper@intux.org>, internals@lists.php.net
In-Reply-To: <1357343140.20040629195517@marcus-boerger.de>
References: <000b01c45d02$95eab040$9f00a8c0@silverbox>
	 <1357343140.20040629195517@marcus-boerger.de>
Content-Type: text/plain
Message-ID: <1088553055.2185.31.camel@mesa>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.6 
Date: Wed, 30 Jun 2004 00:50:55 +0100
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] __Destruct() functionality
From: gareth@fission.org.uk (Gareth Ardron)

On Tue, 2004-06-29 at 18:55, 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.

Does the examples I gave you before not count ?

To reiterate:

<?php
// db in this sense is an already initialised database class
// basic wrappers around the mysql functions in my case.
class logger extends db {
	function logEvent($msg){
		// somecode here which uses the parent db class
		// to write the msg to a database
	}
}

class someOtherClass {
	public $log;
	function __destruct(){
		$log->logEvent("leaving someOtherClass");
	}
}

$log = new logger;
$soc = new someOtherClass;
$soc->log = $log;

?>

in this case, the __destruct() function within someOtherClass does
absolutly bugger all.