We should have used exit instead of Exit. (Perl built-in functions do not contain capital letters, and the reserved words that do are all uppercase.) Better yet, we should have called dieinstead of print. Chapter 9. Run-time Exceptions “When you have eliminated the impossible, that which remains, however improbable, must be the truth.” Sherlock Holmes in A Study in Scarlet, by Sir Arthur Conan Doyle I remember when I was writing my first program in an independently- compiled language (Fortran; before that I was just using interpreted BASIC). After much work, I got the program to compile without any errors. In glee, I turned to a co-worker and said, “All right! I’m done now!” A grin came over his face, and he said, “I doubt it.” What awaited me at that point was the evil run-time error. Perl is no slouch in the run-time error reporting department, and in fact, many errors that would occur at compile time in other languages happen at run time in Perl. For example, using a string in a numeric context: a strongly typed language would spot at compile time the attempt to assign a string to a numeric variable, but in Perl a scalar can switch between a string and a number according to whim. We present here our bug-hunting approach to resolving run-time exceptions. There’s no way to know whether you’ve gotten rid of all possible run-time bugs without running your program under every conceivable set of inputs and environmental changes that might possibly affect it.[1]
Note: If you are looking for good and quality webspace to host and run your java application check Actions java hosting services