Req #42132 [Opn->Wfx]: suggest a fix for global object got destructed in output buffer handler
Edit report at https://bugs.php.net/bug.php?id=42132&edit=1
ID: 42132
Updated by: mike@php.net
Reported by: xuefer at gmail dot com
Summary: suggest a fix for global object got destructed in
output buffer handler
-Status: Open
+Status: Wont fix
Type: Feature/Change Request
-Package: Feature/Change Request
+Package: *General Issues
Operating System: gentoo linux
PHP Version: 5CVS-2007-07-28 (CVS)
Block user comment: N
Private report: N
New Comment:
http://3v4l.org/2ZsYF
Previous Comments:
------------------------------------------------------------------------
[2007-07-29 23:41:10] jani@php.net
See also bug #39546 and bug #39629
------------------------------------------------------------------------
[2007-07-28 14:30:02] xuefer at gmail dot com
Description:
------------
it seems that the implicit ob_end_flush() is called after object destructions.
uncomment any ONE of the comments gives "okay". but this is not the official trick that
supported by php.
the php bug system suggest me this bug is by design in #39546 #39629 etc.
there's many register_xxx arround my php files, which install data into a global object, and
the output buffer handler will inject the data into the output in the correct place. if this bug is
not fixed, the only way i can do is to rewrite the object into array/functions
anyway, i have a suggested fix to change the work flow a bit:
1. flush and pop all OBs but leave 1 top OB on shutdown
2. destruct objects
3. flush the last OB if there's any
no matter if this bug is gonna be fixed, there shall be a page that give explanation and work
arround to this issue.
Reproduce code:
---------------
<?php
class Obj
{
}
function callback($content)
{
return isset($GLOBALS['a']) ? $content : 'oops';
}
ob_start('callback');
$a = new Obj();
//$b = $a;
echo 'okay';
//ob_end_flush();
?>
Expected result:
----------------
okay
Actual result:
--------------
oops
------------------------------------------------------------------------
--
Edit this bug report at https://bugs.php.net/bug.php?id=42132&edit=1
Thread (3 messages)