On Wednesday, 20 February 2013 at 07:54:19 UTC, monarch_dodra
wrote:
Note that an Error is not an Exception, and an Exception is not
an Error. Both, however, are Throwable's. If you want to catch
an *anything*, then catch a Throwable.
As already mentioned though, catching an Error is not something
you usually do, as their existence implies an already
catastrophic state. At best, they can be used to
semi-gracefully die.
Yeah I am trying to catch a range violations thrown inside D
Dlls, which if not trapped somehow manually, crash very
ungracefully :).
