意外的'endwhile' (T_ENDWHILE)

语法使用冒号-如果没有冒号，就会发生上述错误。

<?php while($query->fetch()): ?>
 ....
<?php endwhile; ?>

这种语法的替代方法是使用花括号:

<?php while($query->fetch()) { ?>
  ....
<?php } ?>

http://php.net/manual/en/control-structures.while.php

意想不到的T_LNUMBER

令牌T_LNUMBER指向一个“长”/ number。

Invalid variable names In PHP, and most other programming languages, variables cannot start with a number. The first character must be alphabetic or an underscore. $1 // Bad $_1 // Good Quite often comes up for using preg_replace-placeholders "$1" in PHP context: # ↓ ⇓ ↓ preg_replace("/#(\w+)/e", strtopupper($1) ) Where the callback should have been quoted. (Now the /e regex flag has been deprecated. But it's sometimes still misused in preg_replace_callback functions.) The same identifier constraint applies to object properties, btw. ↓ $json->0->value While the tokenizer/parser does not allow a literal $1 as variable name, one could use ${1} or ${"1"}. Which is a syntactic workaround for non-standard identifiers. (It's best to think of it as a local scope lookup. But generally: prefer plain arrays for such cases!) Amusingly, but very much not recommended, PHPs parser allows Unicode-identifiers; such that $➊ would be valid. (Unlike a literal 1). Stray array entry An unexpected long can also occur for array declarations - when missing , commas: # ↓ ↓ $xy = array(1 2 3); Or likewise function calls and declarations, and other constructs: func(1, 2 3); function xy($z 2); for ($i=2 3<$z) So usually there's one of ; or , missing for separating lists or expressions. Misquoted HTML And again, misquoted strings are a frequent source of stray numbers: # ↓ ↓ echo "<td colspan="3">something bad</td>"; Such cases should be treated more or less like Unexpected T_STRING errors. Other identifiers Neither functions, classes, nor namespaces can be named beginning with a number either: ↓ function 123shop() { Pretty much the same as for variable names.

意想不到的“=”

这可能是由于在变量名中使用无效字符造成的。变量名称必须遵循以下规则:

变量名与PHP中的其他标签遵循相同的规则。有效变量名以字母或下划线开头，后面跟着任意数量的字母、数字或下划线。作为正则表达式，它可以这样表示:'[a- za - z_ \x7f-\xff][a- za - z0 -9_\x7f-\xff]*'

意外的T_CONSTANT_ENCAPSED_STRING意外的t_encapsed_and_空白

T_CONSTANT_ENCAPSED_STRING和T_ENCAPSED_AND_WHITESPACE是指带引号的“字符串”字面量。

它们在不同的上下文中使用，但语法问题非常相似。t_encaged…警告出现在双引号的字符串上下文中，而T_CONSTANT…字符串经常在普通PHP表达式或语句中出错。

Incorrect variable interpolation And it comes up most frequently for incorrect PHP variable interpolation: ⇓ ⇓ echo "Here comes a $wrong['array'] access"; Quoting arrays keys is a must in PHP context. But in double quoted strings (or HEREDOCs) this is a mistake. The parser complains about the contained single quoted 'string', because it usually expects a literal identifier / key there. More precisely it's valid to use PHP2-style simple syntax within double quotes for array references: echo "This is only $valid[here] ..."; Nested arrays or deeper object references however require the complex curly string expression syntax: echo "Use {$array['as_usual']} with curly syntax."; If unsure, this is commonly safer to use. It's often even considered more readable. And better IDEs actually use distinct syntax colorization for that. Missing concatenation If a string follows an expression, but lacks a concatenation or other operator, then you'll see PHP complain about the string literal: ⇓ print "Hello " . WORLD " !"; While it's obvious to you and me, PHP just can't guess that the string was meant to be appended there. Confusing string quote enclosures The same syntax error occurs when confounding string delimiters. A string started by a single ' or double " quote also ends with the same. ⇓ print "<a href="' . $link . '">click here</a>"; ⌞⎽⎽⎽⎽⎽⎽⎽⎽⌟⌞⎽⎽⎽⎽⎽⎽⎽⎽⎽⎽⎽⌟⌞⎽⎽⎽⎽⎽⎽⎽⎽⎽⎽⎽⎽⎽⎽⎽⌟ That example started with double quotes. But double quotes were also destined for the HTML attributes. The intended concatenation operator within however became interpreted as part of a second string in single quotes. Tip: Set your editor/IDE to use slightly distinct colorization for single and double quoted strings. (It also helps with application logic to prefer e.g. double quoted strings for textual output, and single quoted strings only for constant-like values.) This is a good example where you shouldn't break out of double quotes in the first place. Instead just use proper \" escapes for the HTML attributes´ quotes: print "<a href=\"{$link}\">click here</a>"; While this can also lead to syntax confusion, all better IDEs/editors again help by colorizing the escaped quotes differently. Missing opening quote Equivalently are forgotten opening "/' quotes a recipe for parser errors: ⇓ make_url(login', 'open'); Here the ', ' would become a string literal after a bareword, when obviously login was meant to be a string parameter. Array lists If you miss a , comma in an array creation block, the parser will see two consecutive strings: array( ⇓ "key" => "value" "next" => "....", ); Note that the last line may always contain an extra comma, but overlooking one in between is unforgivable. Which is hard to discover without syntax highlighting. Function parameter lists The same thing for function calls: ⇓ myfunc(123, "text", "and" "more") Runaway strings A common variation are quite simply forgotten string terminators: ⇓ mysql_evil("SELECT * FROM stuffs); print "'ok'"; ⇑ Here PHP complains about two string literals directly following each other. But the real cause is the unclosed previous string of course. HEREDOC indentation Prior PHP 7.3, the heredoc string end delimiter can't be prefixed with spaces: print <<< HTML <link..> HTML; ⇑ Solution: upgrade PHP or find a better hoster.

另请参阅

PHP中关联数组的插值(双引号字符串) 语法错误，意外的T_CONSTANT_ENCAPSED_STRING 语法错误，PHP中意外的T_CONSTANT_ENCAPSED_STRING SQL查询中出现意外的T_CONSTANT_ENCAPSED_STRING错误

对于VS Code的新手，如果你看到语法错误，检查你是否保存了文件。如果你有一个错误的语法，保存文件，然后在不保存的情况下修复语法，VS Code会继续显示错误。只有保存文件后，错误信息才会消失。

意外的'continue' (T_CONTINUE)

Continue是一个语句(如for或if)，必须单独显示。它不能用作表达式的一部分。部分原因是continue不返回值，但在表达式中，每个子表达式都必须产生某个值，因此整个表达式都会产生一个值。这就是语句和表达式的区别。

这意味着continue不能用于三元语句或任何需要返回值的语句。

意外的“中断”(T_BREAK)

休息也是一样;当然可以。它也不能用于表达式上下文，而是一个严格语句(与foreach或if块处于同一级别)。

意外的“返回”(T_RETURN)

对于return来说，这可能更令人惊讶，但这也只是一个块级语句。它确实向更高的作用域/函数返回一个值(或NULL)，但它不作为表达式本身计算。→也就是说:return(return(false);;