Which exception is used internally by ruby

Our mission: to tame production and make you a better, more productive developer. Learn more. When she's not neck-deep in other people's bugs, she enjoys making furniture with traditional hand-tools, reading history and brewing beer in her garage in Seattle. Join our community of kick-ass developers as we learn engineering, DevOps, cloud architecture, and bootstrapping remote software companies.

We're Honeybadger. We'll never send you spam; we will send you cool stuff like exclusive content, memes, and special swag. We're working on something new! Hook Relay gives you Stripe-quality webhooks in minutes.

Sign up for free today! Check out Hook Relay. Ruby's Exception vs StandardError: What's the difference? While it may be tempting to rescue every child of the Exception class, it is generally considered bad practice due to the way the Ruby exception hierarchy is structured. The reason for this is that, while all Ruby exceptions and errors are an extension of the Exception class, many of them are reserved for use internally by Ruby.

For example, SignalException::Interrupt is used to signal that Ctrl-C has been detected during the execution of a script. If you were to rescue every child of the Exception class, then the Interrupt exception wouldn't work as expected. That said, if you do want to rescue every exception that is raised in Ruby, the same begin-rescue block can be used to specifically rescue all Exception exceptions:. Using the above begin-rescue block will rescue every exception and error that is raised, from interrupts to syntax errors, and even memory errors, so use it sparingly and with caution.

The syntax for the rescue statement is:. The code between begin and rescue is where a Ruby exception can occur. If an exception is encountered, the code inside the rescue clause gets executed. For each rescue clause, the raised Ruby exception is compared against each parameter and the match succeeds if the exception in the clause is the same as or a superclass of the thrown exception.

If the thrown Ruby exception does not match any of the specified exception types, the else block gets executed. The ensure block is always executed whether a Ruby exception occurs or not. In the above example, a file is attempted to be opened in the begin block. If the file is found, the else block gets executed. If you've ever gotten a cryptic "stack level too deep" error in Ruby, you've encountered a SystemStackError exception:.

It is impossible to rescue fatal , and it's impossible to raise it artificially. First of all, we'll say it again: don't rescue the Exception class in Ruby. If you must rescue Exception , such as for error reporting, always re-raise the exception promptly:. Fun fact: Rails 5. Join us on our quest to discover all of Ruby's Exceptional Creatures!

Society members will receive new creatures as we discover them we'll be adding more in the coming months. Oh, and you'll learn a lot about Ruby, too. Exception A nebulous monster that can imitate any other creature in the hierarchy. Ruby's Exception class. This will swallow every single exception.

You may also have a look at the following articles to learn more —. Submit Next Question. By signing up, you agree to our Terms of Use and Privacy Policy. Forgot Password? This website or its third-party tools use cookies, which are necessary to its functioning and required to achieve the purposes illustrated in the cookie policy. By closing this banner, scrolling this page, clicking a link or continuing to browse otherwise, you agree to our Privacy Policy.

Ruby Exceptions By Priya Pedamkar. Popular Course in this category. Course Price View Course. Free Software Development Course.