Robert Klemme wrote in post #977344:
>
> Ruby does not have checked exceptions and it provides enough
> mechanisms to deal with exceptions which make wrapping superfluous
> (see below).
> [..]
>
It's very common to want to catch an exception and wrap it in a custom 
class, so you can add some information that is only available locally 
(e.g. parameter values that are probably responsible for the exception). 
That problem is independent of using checked exceptions and has to do 
with the general problem of propagating information up an unwinding 
stack. The way Java allows this is very helpful.

> DRb really seems the only place where a kind of wrapping may make
> sense but even here you probably do not want to wrap exceptions but
> just carry over backtraces, because the exception class may not be
> known to the client.
>
DRb is just one of many situations where you want to raise a new 
exception while retaining all information from the old one. The main 
difference with DRb is that, as you say, you often don't want to retain 
the old object, but only the contents of that object.

-- 
Posted via http://www.ruby-forum.com/.