Lecciones

If you studied at a university, you probably heard theoretical studies extolled as if 99% of graduates would go to engage in scientific research. The next motivational lesson prepared by the CodeGym super specialist will teach you the best things to focus on when learning.

A stack obeys the "first in, last out" principle. In Java, the StackTrace rule says: Remember that the last function called is the first function to end. That is, if function A calls function B, which calls function C, which calls function D, then returning from function B requires that we first return from function C, which requires that we first return from function D.

A stack is like a stack of plates at a cafeteria. If for some reason the third plate from the top catches your fancy, you'll have to remove the top two to get to it. The Java call stack is a special collection that the virtual machine uses to record all function calls. We'll learn how to get the plate we want by completing some tasks involving StackTrace.

Previously, when an error occurred in a method, the program would terminate. Now the Java machine creates a special object (an exception), which stores information about the error. The program exits the current method, then exits the method that called that method, and so on until it reaches the main method. For the program to continue working, the exception must be "caught".

In Java, exceptions are divided into two types: checked and unchecked, i.e. exceptions that must be caught and exceptions that do not have to be caught. By default, all exceptions must be caught. Now we'll try to understand how to work with exceptions thrown by the Java machine.

Exceptions are a very elegant and convenient mechanism for dealing with errors. But to work with them, you must understand some things about Java programming, and you need to get used to how the call stack unwinds. In this lesson, let's look at an example of how to create, throw, and catch exceptions.

By Level 9, CodeGym students have already completed dozens of tasks. But not without some mistakes, right? Previously, the program would terminate if an error occurred. Now Java has exceptions and a special "trap" for exceptions: the try-catch block. Let's complete several tasks involving exceptions while working with numbers, strings, arrays, and collections.

The catch statement, which is used to catch exceptions, can catch multiple exceptions. What does using a single multi-catch block do for you? It makes code simpler and more understandable, eliminates repetition, and is mood-enhancing (this last property is an optional consequence of using multi-catch).

How multi-catch works? If an exception occurs in a try block, execution of the program jumps to the first catch. If the type specified inside the catch statement matches the exception type, then the code inside the {} block starts executing. Otherwise, execution moves to the next catch and the check is repeated. Now let's practice to help reinforce this concept.

At this level, you really need to understand the theory! That's why the professor has a whole heap of references for you. They are mostly, but not exclusively, devoted to exceptions. Let's thank the professor for his efforts, watch some detailed videos, and read useful articles about exceptions, StackTrace, and method signatures.

You don’t have to unplug your brain to prevent a meltdown due to an overabundance of new information. We just need to feed it something simple that’s still interesting. Let’s watch an inspiring speech by Larry Smith about why people fail to have great careers unless they follow their passion and see opportunities instead of obstacles.

Several tasks must be completed at the end of the level. Some of them are more advanced and require student's to be able to google. Or think. Or think and google. Practice completing them day in and day out, and your skills will grow at an incredible speed. They were created especially for IDEA.