Severe error (Fatalerror)
The following subsections discuss the serious mistake of WML Script.
Brightode error (Bytedode Error)
These errors associated with the instructions performed by the WML Script bitcode interpretation, which pointed out the wrong element group, invalid instruction, the parameters used by the instructions, or the instructions cannot be executed.
Verification error (Verification Failed)
Note: The specific bit code in the calling program cannot be verified.
How to happen: Try an external program for each program.
Example: VAR A = 3 * Otherscript # Dothis (param)
Severeness: serious.
Judgment status: When the detection bit code verification is verified.
Workaround: The termination program is interpreted with the WML Script to translate its caller's error signal.
Description: Severe errors occur when calling a library program.
How to happen: Each time you call the library program.
Example: var a = string.format (param)
Severeness: serious.
Judgment status: no
Workaround: The termination program is interpreted with the WML Script to translate its caller's error signal.
Note: The number of call function parameters is not compliant with the number of parameters of the called function.
How to happen: Call external programs.
Example: The compiler is giving an invalid parameter to give instructions, or the number of program parameters called the call change.
Severeness: serious.
Judgment status: no
Severeness: serious.
Solution: Terminate the error signal that is called with the WML Script Explosion.
Note: The required external program is not found in a specific program.
How to happen: Call external programs.
Example: VAR A = 3 * Otherscript # Dothis (param)
Severeness: serious.
Judgment status: no
Solution: Terminate the error signal that is called with the WML Script Explosion.
Explanation: Because errors or specific programs that cannot be repaired in the network server or the specific program is not loaded in the network server.
How to happen: Call external programs.
Example: VAR A = 3 * Otherscript # Dothis (param)
Severeness: serious.
Judgment status: no
Solution: Terminate the error signal that is called with the WML Script Explosion.
Description: Access error, the external program called is protected.
How to happen: call external programs
Example: VAR A = 3 * Otherscript # Dothis (param)
Severeness: serious.
Judgment status: no
Solution: Terminate the error signal that is called with the WML Script Explosion.
Description: Stack Underflow caused by the program error.
How to happen: The program is to take out (POP) an empty bunch
Example: When a group translation generates an error code.
Severeness: serious.
Judgment status: no
Solution: Terminate the error signal that is called with the WML Script Explosion.
Description: Perform calling lang.abort () is an error.
How to happen: Whenever the program calls the lang.abort () function.
Example: Lang.abort ("Unrecoverable Error")
Severeness: serious.
Judgment status: no
Solution: Terminate the error signal that is called with the WML Script Explosion.
Description: The stack overflowing occurs.
How to happen: There are too many program resources or to push too much variable to the calculation. Example: function f | (x) (f (x 1););
Severeness: serious.
Judgment status: no
Solution: Terminate the error signal that is called with the WML Script Explosion.
Note: There is no excess memory available for use.
How to happen: The operating system cannot configure excess space to use it to the interpreter.
Example: function f (x) {
X = X "AbcdefghijklmnopqrStuvxyz";
f (x);
}
Severeness: serious.
Severe error (Fatalerror)
The following subsections discuss the serious mistake of WML Script.
Brightode error (Bytedode Error)
These errors associated with the instructions performed by the WML Script bitcode interpretation, which pointed out the wrong element group, invalid instruction, the parameters used by the instructions, or the instructions cannot be executed.
Verification error (Verification Failed)
Note: The specific bit code in the calling program cannot be verified.
How to happen: Try an external program for each program.
Example: VAR A = 3 * Otherscript # Dothis (param)
Severeness: serious.
Judgment status: When the detection bit code verification is verified.
Workaround: The termination program is interpreted with the WML Script to translate its caller's error signal.
Description: Severe errors occur when calling a library program.
How to happen: Each time you call the library program.
Example: var a = string.format (param)
Severeness: serious.
Judgment status: no
Workaround: The termination program is interpreted with the WML Script to translate its caller's error signal.
Note: The number of call function parameters is not compliant with the number of parameters of the called function.
How to happen: Call external programs.
Example: The compiler is giving an invalid parameter to give instructions, or the number of program parameters called the call change.
Severeness: serious.
Judgment status: no
Severeness: serious.
Solution: Terminate the error signal that is called with the WML Script Explosion.
Note: The required external program is not found in a specific program.
How to happen: Call external programs.
Example: VAR A = 3 * Otherscript # Dothis (param)
Severeness: serious.
Judgment status: no
Solution: Terminate the error signal that is called with the WML Script Explosion.
Explanation: Because errors or specific programs that cannot be repaired in the network server or the specific program is not loaded in the network server.
How to happen: Call external programs.
Example: VAR A = 3 * Otherscript # Dothis (param)
Severeness: serious.
Judgment status: no
Solution: Terminate the error signal that is called with the WML Script Explosion.
Description: Access error, the external program called is protected.
How to happen: call external programs
Example: VAR A = 3 * Otherscript # Dothis (param)
Severeness: serious.
Judgment status: no
Solution: Terminate the error signal that is called with the WML Script Explosion.
Description: Stack Underflow caused by the program error.
How to happen: The program is to take out (POP) an empty reactor: When the group translator generates an error code.
Severeness: serious.
Judgment status: no
Solution: Terminate the error signal that is called with the WML Script Explosion.
Description: Perform calling lang.abort () is an error.
How to happen: Whenever the program calls the lang.abort () function.
Example: Lang.abort ("Unrecoverable Error")
Severeness: serious.
Judgment status: no
Solution: Terminate the error signal that is called with the WML Script Explosion.
Description: The stack overflowing occurs.
How to happen: There are too many program resources or to push too much variable to the calculation.
Example: function f | (x) (f (x 1););
Severeness: serious.
Judgment status: no
Solution: Terminate the error signal that is called with the WML Script Explosion.
Note: There is no excess memory available for use.
How to happen: The operating system cannot configure excess space to use it to the interpreter.
Example: function f (x) {
X = X "AbcdefghijklmnopqrStuvxyz";
f (x);
}
Severeness: serious.
Judgment status: No solution: The end program is called with the WML Script Explosion. Note: How to perform the execution of the user (such as the RESET button) happens: at any time. Example: When the application is executing is the user presses the RESET button. Severeness: serious. Judgment status: No solution: The end program is called with the WML Script Explosion. Description: External serious errors occurred in execution. How to happen: Always. Example: weak electricity, automatic system. Severeness: serious. Judgment status: No solution: The end program is called with the WML Script Explosion. 2. General error (Nonfatal Error) The general error of WML Script: Computational Error These errors are due to WML Script mathematical operations. In addition to zero (Divide By Zero): How to happen to zero: When there is a condition in the program. Example: var a = 10; var b = 0; var x = a / b; var y = a div b; var z = a% b; A / = B; severity: General. Judgment status: High solution: The result is Invalid. Note: How to happen to zero: The program is to perform floating point calculations. Example: var A = float.Precision (); var b = float.Precision (); var c = a * b Severity: General. Judgment status: High, is very difficult in certain conditions. Workaround: The result is a floating point value 0.0 constant reference error (Constant Reference Error) Description: The floating point number of the referred to is not a number. How to happen: The program tries to access a floating point number, but the group transcript generates the floating point constant of Not A Number. Example: Refer to the floating point constant. Severeness: General. Judgment status: High Solution: This produces an Invalid value. Description: The floating point of the reference is not an infinite floating point constant. How to happen: The program tries to access a floating point number, but the group transpiler generates an infinite or infinite floating point constant. Example: Refer to the floating point constant. Severeness: General. Judgment status: High Solution: This produces an Invalid value. Description: Refer to the error that will occur with reference to floating point values. How to happen: The program needs to use floating point values but the environment value supports integer values. Example: VAR A = 3.14; Severity: General Judicial Status: High Solution: This generates an invalid value. Conversion error This error occurs related to the automatic conversion supported by WML Script. Note: To convert to an integer value, this value exceeds the range (positive or negative) that can be accepted. How to happen: The program tries to automatically convert into an integer.
