What problems should php trycatch solve?

I know that php has an exception handling. Baidu once told everyone how to write the syntax. Use the above set as needed. However, I have not found an article to tell you why trycatch is used. what problems does it mean. We can see that it can reduce the code by "if... else"... knowing that php has an exception handling problem. once Baidu goes through it, it will tell you how to write the syntax. Use the above set as needed. However, I have not found an article to tell you why try catch is used. what problems does it mean to solve. We can see that this can reduce the "wild path like if... else" of the code, but we didn't continue to elaborate on it.
Do you know? keep searching for answers and always come back to pay attention to the answers to this question.

Reply content:

I know that php has an exception handling. Baidu once told everyone how to write the syntax. Use the above set as needed. However, I have not found an article to tell you why try catch is used. what problems does it mean to solve. We can see that this can reduce the "wild path like if... else" of the code, but we didn't continue to elaborate on it.
Do you know? keep searching for answers and always come back to pay attention to the answers to this question.

In addition to processing all input and computation results as per our needs, it is also very important to process incorrect input or abnormal computation results.

The original exception handling is of course the use of the If control statement you mentioned. this method is too simple and requires not only writing a lot of repeated code, the code for handling exceptions is too large, causing bugs to be hidden.

The exception handling mechanism at the higher level is an error mechanism. The error mechanism can provide a method to execute the specified code segment when an exception occurs, solving the problem of using If to identify a lot of bloated and ugly exception handling code. However, the error handling mechanism only provides exception handling procedures and does not provide maintenance related to exception environments such as Stack processing. Therefore, the error handling mechanism is only applicable to flat programming such as process-oriented.

The next layer is the exception handling mechanism, that is, Try Catch. compared with error handling, exception handling can retain and implement Stack Control, not only can our exception handling code stay close to the areas where exceptions may occur, but also allow programmers not to worry too much about context maintenance when exceptions occur. Especially in the stack structure with many layers, the exception mechanism can display the underlying layer of the stack to handle the upper layer exceptions.

Separate the error code and process the error code.

This gives high-level functions the opportunity to handle errors.