Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:41330
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.14 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=cc:message-id:from:to:in-reply-to:content-type
         :content-transfer-encoding:mime-version:subject:date:references
         :x-mailer:sender;
        b=dkn2/KjudUPXqhIidAf/7nnIC82BgA+HnVdgmqRaQJWaVr6MHtoDaYbqaeGS9bo7sJ
         suW8JzlXd0MoyoZ40I13dnmTzWvH1crpMf5o2skhcSiZDaBqMbD5ET2rGqnvsq+HW5BY
         Xo5vQ/xxAkSpXEKhIwRjZdkbmBQeBxyR/QLko=
Cc: internals@lists.php.net
Message-ID: <70F4E63C-CA1A-4811-ADE9-F322C467926F@filemobile.com>
To: Larry Garfield <larry@garfieldtech.com>
In-Reply-To: <200810222123.58206.larry@garfieldtech.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Thu, 23 Oct 2008 00:09:35 -0400
References: <A8.C0.10341.9DB7EF84@pb1.pair.com> <cd5680a20810212300q322c2255y2a71ed753c791449@mail.gmail.com> <48FED6DA.2090400@naenius.com> <200810222123.58206.larry@garfieldtech.com>
Sender: Evert Pot - Rooftop Solutions <evertpot@gmail.com>
Subject: Re: [PHP-DEV] Destructor Order
From: evert@filemobile.com (Evert | Filemobile)

> I believe the "end of your script" part is the problem.  Imagine you  
> have some
> object (say, ActiveRecord style) that writes itself to the database  
> when it's
> destroyed if the data has been modified.  Now cache that object in a  
> static
> variable somewhere for performance.  You're also using PDO, so your  
> database
> connection is a global or singleton instance of the PDO class.
>
> Then your script reaches the end.  Does your object get destroyed and
> therefore saved to the database before or after the PDO object goes  
> away?  I
> don't actually know.
>
> I'm not saying that manual destructor order is the correct way to  
> deal with
> that issue necessarily, but I think that's the sort of use case it's  
> intended
> to address.

If you want to treat a PHP script as a traditional application, you  
should be prepared to unset() and keep references of everything  
yourself. Relying on the garbage collector for your business logic to  
work is just bad design.

I'd personally always explicitly do a ->saveObject in similar  
situations as its predictable and quite frankly never found a use for  
a destructor other than debugging..

Sounds like a subject that doesn't belong on PHP-DEV in any event.

Evert