@@ -37,26 +37,26 @@ use instead of e.g. :phpfunction:`var_dump`. By using it, you'll gain:
37
37
reference structure of your data;
38
38
* Ability to operate in the context of an output buffering handler.
39
39
40
- ``dump() `` is just a thin wrapper and more convenient way to call
40
+ ``dump() `` is just a thin wrapper and a more convenient way to call
41
41
:method: `VarDumper::dump() <Symfony\\ Component\\ VarDumper\\ VarDumper::dump> `.
42
42
You can change the behavior of this function by calling
43
43
:method: `VarDumper::setHandler($callable) <Symfony\\ Component\\ VarDumper\\ VarDumper::setHandler> `:
44
44
calls to ``dump() `` will then be forwarded to ``$callable ``.
45
45
46
- Output Format and Destination
47
- -----------------------------
46
+ By default, the output format and destination are selected based on your
47
+ current PHP SAPI:
48
48
49
- If you read the `advanced documentation <advanced> `, you'll learn how to
50
- change the format or redirect the output to wherever you want.
51
-
52
- By default, these are selected based on your current PHP SAPI:
53
-
54
- * On the command line (CLI SAPI), the output is written on ``STDERR ``. This
49
+ * On the command line (CLI SAPI), the output is written on ``STDOUT ``. This
55
50
can be surprising to some because this bypasses PHP's output buffering
56
- mechanism. On the other hand, it give the possibility to easily split
57
- dumps from regular output by using pipe redirection;
51
+ mechanism;
58
52
* On other SAPIs, dumps are written as HTML on the regular output.
59
53
54
+ .. note ::
55
+ If you want to catch the dump output as a string, please read the
56
+ `advanced documentation <advanced> ` which contains examples of it.
57
+ You'll also learn how to change the format or redirect the output to
58
+ wherever you want.
59
+
60
60
DebugBundle and Twig Integration
61
61
--------------------------------
62
62
0 commit comments