How to Correctly Understand PHP Errors_PHP Tutorial

Brief description: No matter how careful we are when writing programs, mistakes are inevitable. These errors usually confuse the PHP compiler. Compiler error messages are not only useless but often frustrating if developers don't understand what they mean.
No matter how careful we are when writing programs, mistakes are inevitable. These errors usually confuse the PHP compiler. Compiler error messages are not only useless but often frustrating if developers don't understand what they mean.
When compiling a PHP script, the PHP compiler will do its best to report the first problem it encounters. This creates a problem: PHP can only recognize the error when it occurs (this problem is described in detail later in this article). It is for this reason that the compiler points out that the line in error may appear to be syntactically correct on the surface, or it may be a line that does not exist at all!
Better understanding of error messages can significantly save time spent identifying and correcting erroneous content. Therefore, in this article, I will try to clarify the many different types of PHP error messages and how to correctly understand the meaning of various error messages during the development process.
The content described in this article has nothing to do with the version of PHP you are using, because the various errors described in this article are not limited to specific errors in a particular version. In addition, we assume that you are a junior or intermediate programmer and have been engaged in programming for half a year or a year. How the compiler works
To understand why the compiler reports an error on a certain line, you must first understand the mechanism by which the compiler parses PHP code. I'm not going to go into detail about this in this article, but we will discuss some simple concepts that are more likely to lead to errors.
Variable declaration
If you declare a variable in a statement, the specific method is as follows:
$variable = 'value';
The compiler first finds the value of the right half of the statement (i.e., etc. everything to the right of the number). In some programming books, this is represented as the RHS (right half) of the statement. It is this part of the statement that often causes errors. If you use incorrect syntax, you will get a parsing error.
Parse error
Parse error: unexpected T_WHILE in c:program filesapache groupapachehtdocsscript.php on line 19
Parse errors keep appearing one after another every time the previous error is determined. Because PHP stops executing the script after the first parsing error, debugging and correcting this series of errors can often be particularly tiresome.
Also, parsing errors have very little information, with almost no reporting of the line number where the error occurred. The specific reason is that when an error occurs, the compiler determines that the syntax of several lines should look valid until it encounters invalid syntax. The most likely case is that predefined words are used in the expression, such as;
while = 10; // Bad ? while is a predefined word and cannot be assigned to a value

http://www.bkjia.com/PHPjc/632430.htmlwww.bkjia.comtruehttp: //www.bkjia.com/PHPjc/632430.htmlTechArticleBrief description: When we write programs, no matter how careful we are, mistakes are always inevitable. These errors usually confuse the PHP compiler. If developers cannot understand compiler error messages...