意想不到的T_IS_EQUAL 意想不到的T_IS_GREATER_OR_EQUAL 意想不到的T_IS_IDENTICAL 意想不到的T_IS_NOT_EQUAL 意想不到的T_IS_NOT_IDENTICAL 意想不到的T_IS_SMALLER_OR_EQUAL 意想不到的< 意想不到的>

比较运算符，如==，>=，===，!=，<>，!==和<=或<和>，主要应该只在表达式中使用，例如if表达式。如果解析器抱怨它们，那么通常意味着它们周围的paren不正确或不匹配()。

Parens grouping In particular for if statements with multiple comparisons you must take care to correctly count opening and closing parenthesis: ⇓ if (($foo < 7) && $bar) > 5 || $baz < 9) { ... } ↑ Here the if condition here was already terminated by the ) Once your comparisons become sufficiently complex it often helps to split it up into multiple and nested if constructs rather. isset() mashed with comparing A common newcomer is pitfal is trying to combine isset() or empty() with comparisons: ⇓ if (empty($_POST["var"] == 1)) { Or even: ⇓ if (isset($variable !== "value")) { This doesn't make sense to PHP, because isset and empty are language constructs that only accept variable names. It doesn't make sense to compare the result either, because the output is only/already a boolean. Confusing >= greater-or-equal with => array operator Both operators look somewhat similar, so they sometimes get mixed up: ⇓ if ($var => 5) { ... } You only need to remember that this comparison operator is called "greater than or equal" to get it right. See also: If statement structure in PHP Nothing to compare against You also can't combine two comparisons if they pertain the same variable name: ⇓ if ($xyz > 5 and < 100) PHP can't deduce that you meant to compare the initial variable again. Expressions are usually paired according to operator precedence, so by the time the < is seen, there'd be only a boolean result left from the original variable. See also: unexpected T_IS_SMALLER_OR_EQUAL Comparison chains You can't compare against a variable with a row of operators: ⇓ $reult = (5 < $x < 10); This has to be broken up into two comparisons, each against $x. This is actually more a case of blacklisted expressions (due to equivalent operator associativity). It's syntactically valid in a few C-style languages, but PHP wouldn't interpret it as expected comparison chain either. Unexpected > Unexpected < The greater than > or less than < operators don't have a custom T_XXX tokenizer name. And while they can be misplaced like all they others, you more often see the parser complain about them for misquoted strings and mashed HTML: ⇓ print "<a href='z">Hello</a>"; ↑ This amounts to a string "<a href='z" being compared > to a literal constant Hello and then another < comparison. Or that's at least how PHP sees it. The actual cause and syntax mistake was the premature string " termination. It's also not possible to nest PHP start tags: <?php echo <?php my_func(); ?> ↑

参见:

php T_IS_NOT_EQUAL错误 语法错误，意外的T_IS_EQUAL 返回语句的语法错误 http://forums.phpfreaks.com/topic/96891-parse-error-syntax-error-unexpected-t-is-not-identical-expecting-or/

意想不到的T_STRING

T_STRING有点用词不当。它不引用引用的“字符串”。这意味着遇到了原始标识符。这可以是空白的单词、剩余的CONSTANT或函数名、被遗忘的不带引号的字符串或任何纯文本。

Misquoted strings This syntax error is most common for misquoted string values however. Any unescaped and stray " or ' quote will form an invalid expression: ⇓ ⇓ echo "<a href="http://example.com">click here</a>"; Syntax highlighting will make such mistakes super obvious. It's important to remember to use backslashes for escaping \" double quotes, or \' single quotes - depending on which was used as string enclosure. For convenience you should prefer outer single quotes when outputting plain HTML with double quotes within. Use double quoted strings if you want to interpolate variables, but then watch out for escaping literal " double quotes. For lengthier output, prefer multiple echo/print lines instead of escaping in and out. Better yet consider a HEREDOC section. Another example is using PHP entry inside HTML code generated with PHP: $text = '<div>some text with <?php echo 'some php entry' ?></div>' This happens if $text is large with many lines and developer does not see the whole PHP variable value and focus on the piece of code forgetting about its source. Example is here See also What is the difference between single-quoted and double-quoted strings in PHP?. Unclosed strings If you miss a closing " then a syntax error typically materializes later. An unterminated string will often consume a bit of code until the next intended string value: ⇓ echo "Some text", $a_variable, "and some runaway string ; success("finished"); ⇯ It's not just literal T_STRINGs which the parser may protest then. Another frequent variation is an Unexpected '>' for unquoted literal HTML. Non-programming string quotes If you copy and paste code from a blog or website, you sometimes end up with invalid code. Typographic quotes aren't what PHP expects: $text = ’Something something..’ + ”these ain't quotes”; Typographic/smart quotes are Unicode symbols. PHP treats them as part of adjoining alphanumeric text. For example ”these is interpreted as a constant identifier. But any following text literal is then seen as a bareword/T_STRING by the parser. The missing semicolon; again If you have an unterminated expression in previous lines, then any following statement or language construct gets seen as raw identifier: ⇓ func1() function2(); PHP just can't know if you meant to run two functions after another, or if you meant to multiply their results, add them, compare them, or only run one || or the other. Short open tags and <?xml headers in PHP scripts This is rather uncommon. But if short_open_tags are enabled, then you can't begin your PHP scripts with an XML declaration: ⇓ <?xml version="1.0"?> PHP will see the <? and reclaim it for itself. It won't understand what the stray xml was meant for. It'll get interpreted as constant. But the version will be seen as another literal/constant. And since the parser can't make sense of two subsequent literals/values without an expression operator in between, that'll be a parser failure. Invisible Unicode characters A most hideous cause for syntax errors are Unicode symbols, such as the non-breaking space. PHP allows Unicode characters as identifier names. If you get a T_STRING parser complaint for wholly unsuspicious code like: <?php print 123; You need to break out another text editor. Or an hexeditor even. What looks like plain spaces and newlines here, may contain invisible constants. Java-based IDEs are sometimes oblivious to an UTF-8 BOM mangled within, zero-width spaces, paragraph separators, etc. Try to reedit everything, remove whitespace and add normal spaces back in. You can narrow it down with with adding redundant ; statement separators at each line start: <?php ;print 123; The extra ; semicolon here will convert the preceding invisible character into an undefined constant reference (expression as statement). Which in return makes PHP produce a helpful notice. The `$` sign missing in front of variable names Variables in PHP are represented by a dollar sign followed by the name of the variable. The dollar sign ($) is a sigil that marks the identifier as a name of a variable. Without this sigil, the identifier could be a language keyword or a constant. This is a common error when the PHP code was "translated" from code written in another language (C, Java, JavaScript, etc.). In such cases, a declaration of the variable type (when the original code was written in a language that uses typed variables) could also sneak out and produce this error. Escaped Quotation marks If you use \ in a string, it has a special meaning. This is called an "Escape Character" and normally tells the parser to take the next character literally. Example: echo 'Jim said \'Hello\''; will print Jim said 'hello' If you escape the closing quote of a string, the closing quote will be taken literally and not as intended, i.e. as a printable quote as part of the string and not close the string. This will show as a parse error commonly after you open the next string or at the end of the script. Very common error when specifiying paths in Windows: "C:\xampp\htdocs\" is wrong. You need "C:\\xampp\\htdocs\\". Typed properties You need PHP ≥7.4 to use property typing such as: public stdClass $obj;

意想不到的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 {

意想不到的(

现在，在过时的PHP版本中经常可以看到意外的[array括号]。短数组语法从PHP >= 5.4开始可用。旧的安装只支持array()。

$php53 = array(1, 2, 3);
$php54 = [1, 2, 3];
         ⇑

数组函数结果解引用同样不适用于旧的PHP版本:

$result = get_whatever()["key"];
                      ⇑

这个错误在PHP中意味着什么?-“语法错误，意外的\[”显示了最常见和实用的解决方案。

不过，最好还是升级PHP安装。对于共享网络托管计划，首先要研究是否可以使用SetHandler php5 56-fcgi来启用新的运行时。

参见:

对函数result→进行解引用的PHP语法，从PHP 5.4开始可能 PHP语法错误，意外的“[” 数组的简写:是否存在像{}或[]这样的文字语法? PHP 5.3.10 vs PHP 5.5.3语法错误 数组()和[]的区别 PHP数组语法解析错误

顺便说一下，如果你对老版本和慢版本的PHP很感兴趣的话，还有预处理器和PHP 5.4语法下转换器。

导致意外语法错误的其他原因

如果不是PHP版本不匹配，那么通常是一个简单的拼写错误或新手语法错误:

You can't use array property declarations/expressions in classes, not even in PHP 7. protected $var["x"] = "Nope"; ⇑ Confusing [ with opening curly braces { or parentheses ( is a common oversight. foreach [$a as $b) ⇑ Or even: function foobar[$a, $b, $c] { ⇑ Or trying to dereference constants (before PHP 5.6) as arrays: $var = const[123]; ⇑ At least PHP interprets that const as a constant name. If you meant to access an array variable (which is the typical cause here), then add the leading $ sigil - so it becomes a $varname. You are trying to use the global keyword on a member of an associative array. This is not valid syntax: global $var['key'];

结束方括号

这种情况比较少见，但是终止数组[括号]也会出现语法错误。

同样，与)括号或}大括号不匹配是常见的: 函数foobar($a， $b， $c] { ⇑ 或者试图结束一个没有数组的数组: $var = 2]; 这通常发生在多行和嵌套数组声明中。 $数组=[1,2,3],4(5、6 (7 [8][9 10]],11),12]],15); ⇑ 如果是，请使用IDE进行括号匹配以查找任何过早的]数组闭包。至少使用更多的空格和换行来缩小范围。

意想不到的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

意想不到的“。”

如果您试图在不受支持的PHP版本中使用splat操作符(…)，就会发生这种情况。

．.． 首次在PHP 5.6中可用来捕获函数的可变数量的参数:

function concatenate($transform, ...$strings) {
    $string = '';
    foreach($strings as $piece) {
        $string .= $piece;
    }
    return($transform($string));
}

echo concatenate("strtoupper", "I'd ", "like ", 4 + 2, " apples");
// This would print:
// I'D LIKE 6 APPLES

在PHP 7.4中，可以将它用于Array表达式。

$parts = ['apple', 'pear'];
$fruits = ['banana', 'orange', ...$parts, 'watermelon'];
// ['banana', 'orange', 'apple', 'pear', 'watermelon'];