Doc #53290 [Opn->Bgs]: Doc issue
| From: | aharvey@php.net | Date: | Wed, 10 Nov 2010 10:45:41 +0000 |
| Subject: | Doc #53290 [Opn->Bgs]: Doc issue | ||
| References: | 1 | Groups: | php.doc.bugs |
| Request: | Send a blank email to doc-bugs+get-5517@lists.php.net to get a copy of this message | ||
Edit report at http://bugs.php.net/bug.php?id=53290&edit=1
ID: 53290
Updated by: aharvey@php.net
Reported by: oxygenus at gmail dot com
Summary: Doc issue
-Status: Open
+Status: Bogus
Type: Documentation Problem
Package: *General Issues
Operating System: Irrelevant
PHP Version: Irrelevant
Block user comment: N
New Comment:
The note means exactly what it says: you can't use
var_export($var, true) within an ob_start() callback function. You can
use it as per normal with output buffering; it only refers to that very
specific case.
Looks clear enough to me -> closing.
Previous Comments:
------------------------------------------------------------------------
[2010-11-10 11:35:39] oxygenus at gmail dot com
Description:
------------
If used and set to TRUE, var_export() will return the variable
representation
instead of outputing it.
Note:
This function uses internal output buffering with this parameter so it
can not
be used inside an ob_start() callback function.
What does that Note: stand for? It already says on the param what it
does. If
nothing is sent to the output...then who is that note going to help?
People
passing that param already expect a certain behaviour, and are some
trying to
stay away from ob_start in the first place.
---
From manual page: http://www.php.net/function.var-export#Parameters
---
Test script:
---------------
What test script? Doc issue.
Expected result:
----------------
Doc issue
Actual result:
--------------
Doc issue
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/bug.php?id=53290&edit=1