|
php.net | support | documentation | report a bug | advanced search | search howto | statistics | random bug | login |
PatchesPull RequestsHistoryAllCommentsChangesGit/SVN commits
[2000-02-23 18:09 UTC] sbeam at beeline dot net
[2000-02-29 19:03 UTC] sbeam at beeline dot net
[2000-07-23 14:15 UTC] stas at cvs dot php dot net
[2000-08-15 09:36 UTC] waldschrott@php.net
|
|||||||||||||||||||||||||||
Copyright © 2001-2026 The PHP GroupAll rights reserved. |
Last updated: Sun Oct 11 21:00:02 2026 UTC |
parsing or syntax errors sometimes produce a complete parser bailout, giving the user "Document contains no data". Usually we get "parse error at line XX" as expected but with certain types of errors, in certan combinations, we just get the whole lotta nothing. Mostly these are unmatched single quotes, brackets and parens. Following are some complete scripts that reliably cause this on our system: #1: <?php echo "great " . ' googily . " moogily"; ?> ============= #2: <?php function foo() { return "hello kitty"; } echo foo); ?> =========== #3: <?php function foo() return "hello kitty"; } echo foo(); ?> This might seem like a trivial thing since these are so obvious but in a large script it makes it basically impossible to track down several errors like this, especially when hairer complex expressions are used. Here is the relevant section of php.ini: error_reporting = 7 display_errors = On log_errors = On track_errors = On this is how PHP was configured: ./configure --with-mysql --with-pgsql=/usr/bin --with-apache=../apache -enable-track-vars=on Thx!