Merge pull request #2653 from lambdageek/dev/exception_type-1
authormonojenkins <jo.shields+jenkins@xamarin.com>
Mon, 22 Feb 2016 19:30:33 +0000 (19:30 +0000)
committermonojenkins <jo.shields+jenkins@xamarin.com>
Mon, 22 Feb 2016 19:30:33 +0000 (19:30 +0000)
commit71a9582ddaf71b09930cadde06bcbff58f53deb6
treef3d6f34cbbd25156b6e1f62857dad6cf28625397
parent5317fbc0cd0146c84ffab2dc1776ec34cce859c0
parent52ca8647ad3740ee77227322fc85a0bbdb638312
Merge pull request #2653 from lambdageek/dev/exception_type-1

[runtime] Don't access MonoClass::exception_type directly.

Use `mono_class_get_failure ()` and `mono_class_has_failed ()`

This is mostly just cleanup refactoring at this point that will make it easier to change how exception_type is used.

Also from this exercise we've learned that most of the class handling code just cares whether the class has an error or not, not what sort of error it was.
mono/metadata/object.c