In ruby like in most languages an exception is a way to convey that something went wrong.
Ruby raise exception in initialize.
Rescue clause is used to handle the exceptions created by raise.
In a nutshell every custom ruby exception should extend standarderror rather than the exception class the reason for this is outlined in exception handling in ruby with this in mind the simplest custom exception class that we can define will look something like this.
None of ruby s standard exceptions fit so your best bet is to create a new kind of exception.
By providing exception raise and discouraging kernel raise there s no sufficient way to raise pre allocated exceptions.
To do exception handling we enclose the code that could raise an exception in a begin end block and use one or more rescue clauses to tell ruby the types of exceptions we want to handle.
The begin is omitted and the entire body of the method is subject to exception handling ending.
While some languages only use exceptions for truly exceptional circumstances like run time errors ruby uses exceptions for a wide variety of errors and unexpected results.
It is to be noted that the body of a method definition is an implicit begin end block.
Syntax begin rescue onetypeofexception rescue anothertypeofexception else other exceptions ensure always will be executed end.
If we really need to emphasize oo way in raising exception as you claim i d rather add exception raise i e.
We enclose the code that could raise an exception in a begin end block and use rescue clauses to tell ruby the types of exceptions we want to handle.
Kernel raise takes either exception class or exception instance.
Ruby s built in exceptions are great but they don t cover every possible use case.