On 18 May 2015 at 15:39, Levi Morrison <[email protected]> wrote:
>
> I wouldn't group
> TypeException in the same subtree as ParseException, for instance. One
> happens at compile time and the other at run time, which means the
> intent in what you catch is probably quite different.
TypeException is also different the other EngineExceptions, as it's an
exception that people will want to throw from their own code instead
of having a separate UserLandTypeException.
Except for testing, people shouldn't be throwing ParseException or
other EngineExceptions from their code.
cheers
Dan