php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login

go to bug id or search bugs for

Bug #33824 __destruct() mechanism propably incorrect
Submitted: 2005-07-22 18:15 UTC Modified: 2005-07-22 18:27 UTC
From: rusaxakep at mail dot ru Assigned:
Status: Not a bug Package: Class/Object related
PHP Version: 5.0.4 OS: Linux
Private report: No CVE-ID: None
View Add Comment Developer Edit
Welcome back! If you're the original bug submitter, here's where you can edit the bug or add additional notes.
If this is not your bug, you can add a comment by following this link.
If this is your bug, but you forgot your password, you can retrieve your password here.
Password:
Status:
Package:
Bug Type:
Summary:
From: rusaxakep at mail dot ru
New email:
PHP Version: OS:

 

 [2005-07-22 18:15 UTC] rusaxakep at mail dot ru 
Description:
------------
I don't know, maybe is not bug, but in my opinion __destruct() must call in "FIFO" standart's and not "Stack".

I think not correct kill parent's classes, and after child classes.

Need a "tree effect", first kill child's classes (subtree), and after kill parent's classes.

Right? Sorry for bad english, is not native for me.

Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2005-07-22 18:19 UTC] rusaxakep at mail dot ru 
Please ignore previous comment.

I don't know, maybe is not bug, but in my opinion __destruct() must call in "FIFO" standart's and not "STACK".

I think isn't correct kill parent's classes, before child classes.

Right?
 [2005-07-22 18:27 UTC] tony2001@php.net 
There is no exact order of destroying object.
It's implemented in this way because of several reasons and one of the main ones is efficiency.
See more detailed explanations in several reports that were created before - search the bug DB.
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved. 		Last updated: Thu Apr 18 18:01:28 2024 UTC