openfl.errors

The ArgumentError class represents an error that occurs when the arguments supplied in a function do not match the arguments defined for that function. This error occurs, for example, when a function is called with the wrong number of arguments, an argument of the incorrect type, or an invalid argument.

An EOFError exception is thrown when you attempt to read past the end of the available data. For example, an EOFError is thrown when one of the read methods in the IDataInput interface is called and there is insufficient data to satisfy the read request.

The Error class contains information about an error that occurred in a script. In developing OpenFL applications, when you run your compiled code in a debugger, a message displays exceptions of type Error, or of a subclass, to help you troubleshoot the code. You create an Error object by using the Error constructor function. Typically, you throw a new Error object from within a try code block that is caught by a catch code block.

The IOError exception is thrown when some type of input or output failure occurs. For example, an IOError exception is thrown if a read/write operation is attempted on a socket that has not connected or that has become disconnected.

The IllegalOperationError exception is thrown when a method is not implemented or the implementation doesn't cover the current usage.

Permission error is dispatched when the application tries to access a resource without requesting appropriate permissions.

A RangeError exception is thrown when a numeric value is outside the acceptable range.

The SecurityError exception is thrown when some type of security violation takes place.

A TypeError exception is thrown when the actual type of an operand is different from the expected type.