意想不到的(

开括号通常跟在if/foreach/for/array/list这样的语言结构之后，或者开始一个算术表达式。它们在“strings”后，previous()，单独的$和一些典型的声明上下文中都是语法错误的。

Function declaration parameters A rarer occurrence for this error is trying to use expressions as default function parameters. This is not supported, even in PHP7: function header_fallback($value, $expires = time() + 90000) { Parameters in a function declaration can only be literal values or constant expressions. Unlike for function invocations, where you can freely use whatever(1+something()*2), etc. Class property defaults Same thing for class member declarations, where only literal/constant values are allowed, not expressions: class xyz { ⇓ var $default = get_config("xyz_default"); Put such things in the constructor. See also Why don't PHP attributes allow functions? Again note that PHP 7 only allows var $xy = 1 + 2 +3; constant expressions there. JavaScript syntax in PHP Using JavaScript or jQuery syntax won't work in PHP for obvious reasons: <?php ⇓ print $(document).text(); When this happens, it usually indicates an unterminated preceding string; and literal <script> sections leaking into PHP code context. isset(()), empty, key, next, current Both isset() and empty() are language built-ins, not functions. They need to access a variable directly. If you inadvertently add a pair of parentheses too much, then you'd create an expression however: ⇓ if (isset(($_GET["id"]))) { The same applies to any language construct that requires implicit variable name access. These built-ins are part of the language grammar, therefore don't permit decorative extra parentheses. User-level functions that require a variable reference -but get an expression result passed- lead to runtime errors instead.

意想不到的)

Absent function parameter You cannot have stray commas last in a function call. PHP expects a value there and thusly complains about an early closing ) parenthesis. ⇓ callfunc(1, 2, ); A trailing comma is only allowed in array() or list() constructs. Unfinished expressions If you forget something in an arithmetic expression, then the parser gives up. Because how should it possibly interpret that: ⇓ $var = 2 * (1 + ); And if you forgot the closing ) even, then you'd get a complaint about the unexpected semicolon instead. Foreach as constant For forgotten variable $ prefixes in control statements you will see: ↓ ⇓ foreach ($array as wrong) { PHP here sometimes tells you it expected a :: instead. Because a class::$variable could have satisfied the expected $variable expression..

意想不到的{

花括号{和}括起代码块。关于它们的语法错误通常表示一些不正确的嵌套。

Unmatched subexpressions in an if Most commonly unbalanced ( and ) are the cause if the parser complains about the opening curly { appearing too early. A simple example: ⇓ if (($x == $y) && (2 == true) { Count your parentheses or use an IDE which helps with that. Also don't write code without any spaces. Readability counts. { and } in expression context You can't use curly braces in expressions. If you confuse parentheses and curlys, it won't comply to the language grammar: ⇓ $var = 5 * {7 + $x}; There are a few exceptions for identifier construction, such as local scope variable ${references}. Variable variables or curly var expressions This is pretty rare. But you might also get { and } parser complaints for complex variable expressions: ⇓ print "Hello {$world[2{]} !"; Though there's a higher likelihood for an unexpected } in such contexts.

意想不到的}

当出现“意外}”错误时，您多半过早地关闭了代码块。

Last statement in a code block It can happen for any unterminated expression. And if the last line in a function/code block lacks a trailing ; semicolon: function whatever() { doStuff() } ⇧ Here the parser can't tell if you perhaps still wanted to add + 25; to the function result or something else. Invalid block nesting / Forgotten { You'll sometimes see this parser error when a code block was } closed too early, or you forgot an opening { even: function doStuff() { if (true) ⇦ print "yes"; } } ⇧ In above snippet the if didn't have an opening { curly brace. Thus the closing } one below became redundant. And therefore the next closing }, which was intended for the function, was not associable to the original opening { curly brace. Such errors are even harder to find without proper code indentation. Use an IDE and bracket matching.

意料之外的，期待的

需要条件/声明标头和代码块的语言构造将触发此错误。

参数列表 例如，不允许错误声明没有参数列表的函数: ⇓ 函数whatever { ｝ 控制语句条件 你也不能无条件地有一个如果。 ⇓ 如果{ ｝ 这显然说不通。对于常见的疑点，for/foreach, while/do等等，也是如此。 如果您遇到了这种特殊的错误，您绝对应该查找一些手册示例。

意想不到的“=”

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

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

意想不到的美元结束

当PHP谈到“意外的$end”时，这意味着您的代码在解析器期望更多代码时结束了。(如果从字面上理解，这个信息有点误导。它不是关于一个名为“$end”的变量，就像新来者有时认为的那样。它指的是“文件的结束”，EOF。)

原因:代码块/和函数或类声明的{和}不平衡。

它几乎总是缺少一个}花括号来关闭前面的代码块。它的意思是，解析器希望找到一个结束}，但实际上到达了文件的末尾。

同样，使用适当的缩进来避免此类问题。 使用带有括号匹配的IDE，找出}错误的地方。 在大多数ide和文本编辑器中都有快捷键: NetBeans, PhpStorm, Komodo: Ctrl[和Ctrl] Eclipse, Aptana: CtrlShiftP Atom, Sublime: Ctrlm - Zend Studio Ctrlm Geany, notepad++: CtrlB - Joe: CtrlG - Emacs: C-M-n - Vim: %

大多数ide还突出显示匹配的大括号、方括号和圆括号。 这使得检查它们的相关性变得非常容易:

无端接的表达式

对于未结束的表达式或语句，也会出现意外的$end语法/解析器错误:

$var = func（1， ？>EOF

因此，首先查看脚本的末尾。拖尾;在任何PHP脚本中，最后一条语句通常是多余的。但你应该有一个。正是因为它缩小了这些语法问题的范围。特别是在您发现自己在脚本末尾添加了更多语句之后。

缩进的HEREDOC标记

另一种常见情况出现在HEREDOC或NOWDOC字符串中。如果前面有空格、制表符等，终止标记将被忽略:

print <<< END
    Content...
    Content....
  END;
# ↑ terminator isn't exactly at the line start

因此，解析器假定HEREDOC字符串将一直持续到文件的末尾(因此是“意外的$end”)。几乎所有的ide和语法高亮编辑器都会明确显示或发出警告。

转义的引号

如果你在字符串中使用\，它有一个特殊的含义。这称为“转义字符”，通常告诉解析器按字面意思取下一个字符。

示例:echo 'Jim said \'Hello\ ";将打印Jim说'hello'

如果转义字符串的结束引号，结束引号将被字面上理解，而不是像预期的那样，即作为字符串的一部分而不是结束字符串的可打印引号。这通常会在打开下一个字符串后或脚本结束时显示为解析错误。

在Windows中指定路径时非常常见的错误:“C:\xampp\htdocs\”是错误的。你需要“C:\\xampp\\htdocs\\ \”。另外，PHP通常会转换unix风格的路径(例如。“C:/xampp/htdocs/”)到Windows的正确路径。

替代语法

在模板中使用语句/代码块的替代语法时，很少会看到这种语法错误。使用if:和else:和一个缺失的endif;为例。

参见:

PHP语法错误“意外$end” 解析错误:语法错误，在我的PHP代码文件意外结束 解析错误语法错误文件意外结束，使用PHP PHP解析错误:语法错误，CodeIgniter视图中的文件意外结束 解析错误:语法错误，文件意外结束(注册脚本) “解析错误:语法错误，意外$end”为我的uni注册分配 修复PHP错误:PHP错误#3:文件意外结束

意想不到的T_IF 意想不到的T_FOREACH 意想不到的T_FOR 意想不到的T_WHILE 意想不到的T_DO 意想不到的T_ECHO

控制结构，如if、foreach、for、while、list、global、return、do、print、echo只能作为语句使用。它们通常单独驻留在一行上。

Semicolon; where you at? Pretty universally have you missed a semicolon in the previous line if the parser complains about a control statement: ⇓ $x = myfunc() if (true) { Solution: look into the previous line; add semicolon. Class declarations Another location where this occurs is in class declarations. In the class section you can only list property initializations and method sections. No code may reside there. class xyz { if (true) {} foreach ($var) {} Such syntax errors commonly materialize for incorrectly nested { and }. In particular when function code blocks got closed too early. Statements in expression context Most language constructs can only be used as statements. They aren't meant to be placed inside other expressions: ⇓ $var = array(1, 2, foreach($else as $_), 5, 6); Likewise can't you use an if in strings, math expressions or elsewhere: ⇓ print "Oh, " . if (true) { "you!" } . " won't work"; // Use a ternary condition here instead, when versed enough. For embedding if-like conditions in an expression specifically, you often want to use a ?: ternary evaluation. The same applies to for, while, global, echo and a lesser extend list. ⇓ echo 123, echo 567, "huh?"; Whereas print() is a language built-in that may be used in expression context. (But rarely makes sense.) Reserved keywords as identifiers You also can't use do or if and other language constructs for user-defined functions or class names. (Perhaps in PHP 7. But even then it wouldn't be advisable.) Your have a semi-colon instead of a colon (:) or curly bracket ({) after your control block Control structures are typically wrapped in curly braces (but colons can be used in an alternative syntax) to represent their scope. If you accidentally use a semi-colon you prematurely close that block resulting in your closing statement throwing an error.

    foreach ($errors as $error); <-- should be : or {

意想不到的T_VARIABLE

一个“意外的T_VARIABLE”意味着有一个字面的$变量名，它不适合当前表达式/语句结构。

Missing semicolon It most commonly indicates a missing semicolon in the previous line. Variable assignments following a statement are a good indicator where to look: ⇓ func1() $var = 1 + 2; # parse error in line +2 String concatenation A frequent mishap are string concatenations with forgotten . operator: ⇓ print "Here comes the value: " $value; Btw, you should prefer string interpolation (basic variables in double quotes) whenever that helps readability. Which avoids these syntax issues. String interpolation is a scripting language core feature. No shame in utilizing it. Ignore any micro-optimization advise about variable . concatenation being faster. It's not. Missing expression operators Of course the same issue can arise in other expressions, for instance arithmetic operations: ⇓ print 4 + 7 $var; PHP can't guess here if the variable should have been added, subtracted or compared etc. Lists Same for syntax lists, like in array populations, where the parser also indicates an expected comma , for example: ⇓ $var = array("1" => $val, $val2, $val3 $val4); Or functions parameter lists: ⇓ function myfunc($param1, $param2 $param3, $param4) Equivalently do you see this with list or global statements, or when lacking a ; semicolon in a for loop. Class declarations This parser error also occurs in class declarations. You can only assign static constants, not expressions. Thus the parser complains about variables as assigned data: class xyz { ⇓ var $value = $_GET["input"]; Unmatched } closing curly braces can in particular lead here. If a method is terminated too early (use proper indentation!), then a stray variable is commonly misplaced into the class declaration body. Variables after identifiers You can also never have a variable follow an identifier directly: ⇓ $this->myFunc$VAR(); Btw, this is a common example where the intention was to use variable variables perhaps. In this case a variable property lookup with $this->{"myFunc$VAR"}(); for example. Take in mind that using variable variables should be the exception. Newcomers often try to use them too casually, even when arrays would be simpler and more appropriate. Missing parentheses after language constructs Hasty typing may lead to forgotten opening or closing parenthesis for if and for and foreach statements: ⇓ foreach $array as $key) { Solution: add the missing opening ( between statement and variable. ⇓ if ($var = pdo_query($sql) { $result = … The curly { brace does not open the code block, without closing the if expression with the ) closing parenthesis first. Else does not expect conditions ⇓ else ($var >= 0) Solution: Remove the conditions from else or use elseif. Need brackets for closure ⇓ function() use $var {} Solution: Add brackets around $var. Invisible whitespace As mentioned in the reference answer on "Invisible stray Unicode" (such as a non-breaking space), you might also see this error for unsuspecting code like: <?php ⇐ $var = new PDO(...); It's rather prevalent in the start of files and for copy-and-pasted code. Check with a hexeditor, if your code does not visually appear to contain a syntax issue.

另请参阅

搜索:意外T_VARIABLE

意想不到的:

1. PHP 8命名参数语法

Unexpected ':'， expected '，' or ')'

如果试图在PHP < 8的版本中使用PHP 8的新命名形参功能，将会出现以下错误:

$table->string(column:'Name');

解决方案:

将PHP版本升级到PHP 8.0.0或更高版本 不要使用命名参数(按照预期的顺序传递参数)

2. 裁剪类::分隔符

以“解析错误:语法错误，意外的‘:’”开头的错误消息可能是由于错误地将类静态引用class::$Variable写成class:$Variable而引起的。