Developing Apama Applications > Developing Apama Applications in EPL > Testing and Tuning EPL > Handling runtime errors
Handling runtime errors
EPL eliminates many runtime errors because of the following:
*Strict, static typing, so there are no class cast exceptions.
*No implicit type conversion so there are no number format exceptions.
*No concept of null, so there are no null pointer exceptions.
However, EPL cannot entirely eliminate runtime errors. For example, you receive a runtime error if you try to divide by zero or specify an array index that is out of bounds. Some runtime errors are obscure. For example:
mySeq.remove(mySeq.indexOf("foo"));
If foo is not in mySeq, indexOf() returns –1, which causes a runtime error.
See also Catching exceptions .
Copyright © Software AG, Darmstadt, Germany and/or Software AG USA Inc., Reston, VA, USA, and/or its Subsidiaries and or/its Affiliates and/or their licensors.
Use, reproduction, transfer, publication or disclosure is prohibited except as specifically provided for in your License Agreement with Software AG.