This README provides brief answers to common questions about exception handling in Java.

• Use try-catch blocks to encapsulate code that may throw exceptions.
• Catch specific exceptions or groups of exceptions to handle them appropriately.
• Optionally, include a finally block for cleanup operations.

• Ensures graceful handling of errors, preventing crashes.
• Provides feedback to users about what went wrong.
• Helps maintain software stability and reliability.

• java.lang.Throwable serves as the superclass for both exceptions and errors.

• java.lang.Exception is the superclass for all exceptions, excluding errors.

• Keywords include try, catch, finally, throw, and throws.

• Includes checked exceptions (Exception class and subclasses) and unchecked exceptions (RuntimeException and its subclasses).

• Yes, statements can be written between try and catch blocks.

• The Try-Catch pattern is commonly used for exception handling.

• The finally block ensures that certain code executes regardless of whether an exception occurred.

• Code in finally may not execute if the JVM exits abruptly or if there's an infinite loop or System.exit() call within try or catch.

• Yes, try without catch is allowed if followed by finally or catch.

• An exception handler is a block of code responsible for catching and handling exceptions.

• Typically found in the main method or methods at the top of the call stack.

• No, try must be followed by finally or catch blocks.

• Starts with Throwable, which has Error and Exception subclasses, with Exception further subclassing into checked and unchecked exceptions.

• First throws ArithmeticException, second prints Infinity due to floating-point behavior.

• Errors are irrecoverable conditions, while exceptions represent errors in code or unexpected conditions.

• Checked exceptions are checked at compile-time, while unchecked exceptions are not.

• java.lang.Exception can handle both checked exceptions.

• throw is used to raise an exception, while throws is used to declare exceptions that a method may throw.

• Use the throw keyword followed by the exception object.

• Must be caught using try-catch or declared using throws in the method signature.

• Use try-catch or declare exceptions using throws in the method signature.

• Extend Exception class or its subclasses to create custom exceptions.

• Separate exception types using the pipe symbol (|).

• Automatically manages resources, closing them at the end of try block.

• Automatically closes declared resources at the end of try block.

• Catch specific exceptions, provide meaningful error messages, log exceptions, and use try-with-resources for resource management.