Editing 2200: Unreachable State
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 8: | Line 8: | ||
==Explanation== | ==Explanation== | ||
+ | {{incomplete|Created by a BOT in an UNREACHABLE STATE, which is also tired. Please mention here why this explanation isn't complete. Do NOT delete this tag too soon.}} | ||
When writing a computer program, developers often need to make assumptions about what state the system could potentially be in at the time the program is executed. For example, a program designed to fetch data from a database requires that the database be accessible at the time it tries to fetch data; if it is not, then the program needs to know how to handle that state, or it might simply hang or crash the system. A good developer will have accounted for this possibility and may give the program a way to fail gracefully; often, this is done by outputting an {{w|error message}} to the user, to tell them what is wrong. | When writing a computer program, developers often need to make assumptions about what state the system could potentially be in at the time the program is executed. For example, a program designed to fetch data from a database requires that the database be accessible at the time it tries to fetch data; if it is not, then the program needs to know how to handle that state, or it might simply hang or crash the system. A good developer will have accounted for this possibility and may give the program a way to fail gracefully; often, this is done by outputting an {{w|error message}} to the user, to tell them what is wrong. |